I also am in the circumstance of having to supply a Mac "version" of my main app. Fortunately, it's only a small subset of the PC App.
I agree that VFP Mac is a dog - really buggy. Unfortunately, since I deal with the advertising/printing industries, where Macs are still predominant - and you get the "pry it from my cold dead fingers" routine from the artists - I have no choice.
Good luck. There are lots of gotchas all over it. Especially - as I'm learning now - in trying to work with views and grids.
>>Yes, I'm using VFPMac 3.0 and trying to complete an application. Here are my questions.
>>
>>Is there anyway to make this dog faster on a PPC? I've upped the Minimum and Preferred memory sizes to triple their original values and it still seems slow.
>>
>>How do I get rid of the Technical Support bar from the Help menu?
>>
>>Under FPMac 2.6 I could go into ResEdit and change the Creator and Type so that my executable would not bring up VFPMac in development by mistake. Is that still necessary? I also used to modify certain resources in the executable in order for it to have a custom icon. Is that still necessary, and how do I do it?
>>
>>Can I change the prompts on the buttons that are on the GETFILE() and PUTFILE() dialogs?
>>
>>Any help, tips, tricks, jokes, etc. would be greatly appreciated...
>>
>>
>>Michael Haggerty
>
>Sorry to say this but...
>VFP Mac was/is a dog. I spent months on it.
>Spend the development money on buying your client a PC. It's cheaper than fixing the code and making it work. Some of the bugs simply can't be fixed.
>I got a fairly sophisticated app working dual platform. The users were Mac people. They tried the PC version one day, and never went back.
Ken B. Matson
GCom2 Solutions