Joe,

We probably need more ammo before we can comment intellegibly, but I never let that stop me before, so . . .

1) VFP's iminent demise is all rumour, apparently generated by both the mis-informed and those pushing other products. The DEVCON of next week and the ongoing build of version 6 (even though many of us want to see 5.x working RIGHT first) should be proof enough.

2) You know VFP. Do you know ACCESS? Would they expect to get someone else, or are they ready to risk this app with you as your "version 0" ACCESS app?

3) Is there any volume to the data to be processed? If so, ACCESS may have CAPACITY problems. VFP has LOADS more capacity than ACCESS.

4) Are there reasonably tight speed requirements? VFP is still the FASTEST on the planet (when done carefull and right, as I assume you know how to do).

5) VFP is at least (guesswork here, but what the hey!) as capable as ACCESS for OLE. Probably more so (since I don't know what "automation" capabilites ACCESS has).

I'm sure people will come up with more, ESPECIALLY if you come up with a little more BACKGROUND.

Cheers,
Jim N

>I'm proposing to develop an application in Visual Fox 5.0 and my client says they're adopting the entire Microsoft Office suite and why can't I do the app in Access???
>
>I NEED AMMO!!!
>Please contribute any good technical reasons why VFox would be preferred over Access...
>
>Thanx a bunch!
>
>P.S. One concern (the usual) was, "Microsoft probably won't be going forward with VFox anyway..."
>
>
>HELP!