Filepro odbc

[Walter Vaughan]

Rod Caddy wrote:

> Walter Vaughan wrote:
>> Rod Caddy wrote:
>>> I have an issue with fp_odbc, background first.  I run the program 
>>> from a windows xp pro system but the data and programs reside on a 
>>> win2000 server.  The access database resides on the c drive of the xp 
>>> machine 
>> I have never had a problem with fpODBC as 
>> long as I had a good channel to the ODBC server. But now as I read it, 
>> it looks to me that you are thinking that you will be using the OBDC 
>> connector on the machine that has the ./dclerk binary on the hard 
>> disk, but instead you need to have a ODBC connnector on the machine 
>> that has the CPU that is executing ./dclerk
>>
>> If it doesn't work that way, I have a serious mis-understanding of how 
>> filePro operates.

> I think I understand what you are saying.  You are saying I need a copy 
> of dclerk on the local pc?  If this is true, I don't understand why I 
> have been able to run filepro from a server batch file with everything 
> on the server.  Unless you are saying fpodbc looks differently at the 
> system than other filepro builds.  Am I way off base?

Can someone explain this more eloqently? The ODBC connector must be running on 
the CPU that is executing the filePro binary. The filePro binary could be stored 
on anything (e.g. a MacOSX server running SAMBA).

Using the screen that you want to run fileproODBC on, you need to make sure ODBC 
sees your database. Click "Start", "Control Panel" (choose Classic View), 
"Adminstrative Tools", "Data Sources (ODBC)". If you don't have a connection 
there, fileProODBC will behave like you are seeing from my experience.