>>>>>>Hi. Can multiple-users of VFP exchange info with multiple users of MS Access? My company has a program written in Access that they want to make a part of my VFP network.
>>>>>
>>>>>If under "exchange info" you mean they write into each others' tables, it can be done, provided all such tables have primary keys, or at least a field which can be used as one. You'd need an ODBC connectstring and the driver for it (which is probably already installed on each workstation, but may be worth checking). The trouble with connecting to Access is that you need a full path to the mdb file in the database= entry, and that path would differ among workstations, unless all workstations map the drive identically, or you use an UNC. If the Access app uses SQL instead of mdb, then it's a lot easier.
>>>>>
>>>>>Just be careful out there, you never know if the authors of the access app may blame your app for some of their own bugs.
>>>>
>>>>Hey, it's ALWAYS Foxpro's fault (grin)
>>>
>>>As I recall, one of the reasons Microsoft bought FoxPro was to include Rushmore Technology into its preeminent product – Access. You remember Access? That was the database product that would allow any Manager to create a relational database application, to insure that his/her business was profitable. At least that is what the Microsoft salesman told a company I worked for. I never met a Microsoft sales type that heard of FoxPro. Working in Silicon Valley allowed me to meet many.
>>
>>Yes, MicroSoft bought Foxpro so they could gut it and replace it with Access. I still remember waiting the 15 minutes it took for the help file to come up in Access 1.1. Yes, the Access that, even now, really doesn't work well with more than about 6-10 people trying to run the same application, the Access that if the .mdb goes south you've not only lost your data, but your code also. Yeah, that Access. (spit)
>
>The prototype of Access I was shown was so slow, I unwittingly put Fox on Microsoft's radar. The technology did not just go into Access, but into SQL Server as I understand it.

I think it was a big deal in SQL2000.


>
>>
>>Actually, my comment was more of a poke at the how it always seems to be Foxpro's fault when other things go wrong - believe me, I've heard it, I'm still hearing it. Machines in the labs are blowing out with blue screens of death while not running Fox? It's VFP's fault. The PHP/VBA/MSSQL not writing out to the SQL tables? VFP's fault. It rained overnight? VFP's fault.