Hi,

I have a small subset of my main app that must run on Macs - built in VFP3.0 for Mac. A couple heads-up's.
(actually - I don't know whether most of these are Mac issues or 3.0 issues as I never worked in Windows 3.0)

1) VFP3.0 MAc is kludgy, slow, bug-ridden, and in general, a PITA.
2) having said that - if you are in a ituation such as I, where you simply MUST support Macs, it is possible - and really not THAT bad to build a relatively simple app that does work and play well cross platform.

Some caveats and issues ....

1 - no outer joins
2 - can't use stored procedures in Database - must pull them out to methods or prgs on BOTH platforms
3 - Mac (or VFP3) doesn't like "hooks" that don't return anything - I had to go in and put "return .t." in all my base hook code
4 - has more issues (bugs?) with working with views
5 - Help sucks
6 - debugger sucks
7 - code editor sucks
8 - missing methods, events, props, and probably lots of other stuff I just haven't run across (as compared to 5.0 and up)

Having said all this - with some massaging and attempting to keep it simple, It is working pretty well for us. Since there seems to be no other reasonable cross-platform alternative, unless you want to switch languages altogether or go SQL back-end with two different languages (ie VFP on PC - 4th dimension or similar on Mac) , there isn't a lot of choice.

One other alternative - if they have a REALLY FAST mac - like a newer G3 - running Soft Windows on the mac does seem to work pretty well and is stable and fast enough running our app to be an OK solution.


>Hello,
>I need to find out if VFP 3.0 a viable tool for the Mac. If you had a requirement to do a relatively simple database with a few screens, would you be comfortable with VFP 3.0, or are there any killer problems you know of?
>Thanks,
>Howie Brown