Access And Visual Fox Pro Problems with ODBC & Windows

[sledge0001]

Hello out there in It world! Here is the delema.. I am presented with multiple problems.
1.. I am able to view all of the reports on any box in the network as long as its Win 98 or below.
2 When i try to view the reports from a Win XP Box I get ODBC Visual fox Pro Errors. They tell me that the tables are not linked. Now tell me if I am wrong but, If the tables were not linked properly I wouldn't be able to view the reports on a Win 98 box right???
3 It also has given me the error saying that it may be used in Exclusive mode . I have checked the Files on the server and they are in shared mode..
4. I have tried re linking all of the tables and have struck out for 2 days.. Any suggestions??

Thanks,
sledge0001
Chas Boyer

 

[bevancoleman]

If you are using odbc, you have setup ODBC on the XP box right?? You should also check to make sure that Fox Pro drivers are installed (part of MDAC which can be installed with Acces or seperatly).

 

[sledge0001]

I believe that the problem I am having is related to the ODBC drivers not being properly configured. Am I looking in the right place ?? Under administrative tools (XP) Data Sources (ODBC).. Should I be adding the The Visual fox pro drivers into the User DSN or the File DSN?? I am fairly new to Access and Have Never used Visual Fox Pro. Under USer DSN I have listed Dbase files, Excel Files and MS access Database Files. Under System and And File DSN I have nothing listed. I appreciate any help that you could give me! !

Thanks again,
Chas (sledge0001)

 

[SQL]

Well it depends on how you linked the tables originally. If you linked them with a specific data source name with Access, that same datasource name must be defined on all the computers for it to find the right tables.

You are looking in the right place though. Try looking on the machine that looks and see if the data source exists there.

 

[sledge0001]

Okay, Im off to crash the server!!! Ill try anything at this point.
sledge0001

 

[sledge0001]

I think the problem I am having is actually linking the dsn files. I have located the dsn files on a box that works. I am understanding more each day.. Hopefully I will haev this figured out before I get canned!
Sledge0001

 

[bevancoleman]

I tend to use System DSN, it's global accoss all users (including LocalSystem/Services) so you dont need to stress about each user having it.

 

[sitka]

Don't forget that linked tables in Access across separate Access databases are dependent on file location not name or relative path.
So if one Access database has a linked table to another Access database and you move the folder both are .mdb's are in you have to delete and rebuild
those links manually in Access '97 or use the wizard in Access 2000.
oops you mentioned that.
Sorry LOL

permissions can kill you to as the .ldb file has to be created and destroyed so authority has to be established on the folder the .mdb's are in.
A good thing to try would be to create a local user account where the Access files are that corresponds with the XP login. Just to check.
And there is another obscure situation when moving accross Domains or Domains/workgoups. This has to do with the account that establishses the
connection on behalf of the Access link. System Environment variables have to explicitly identify both the TEMP and TMP directories and the previous account (Access to Access database communication) needs create/destroy privlages on the TEMP directory. IIS would be a situation where you would create a local syncronizeed IUSER account on the suspect machine, the linked TO machine. It would need these permissions and TEMP file definitions. There are a couple KB references?
But you are not alone, I'm saddled with providing some FoxPro support and I can not stand it. In general the Foxpro provider called Visual FoxPro Driver would be the best bet as in NT there are about 4 different FoxPro drivers listed but I think they all use the same actual driver file but maybe the function is different.
Further there is a situation called trusted connection with SQL ODBC and it may have a parrallel using ODBC from a Foxpro app to Access. What this does is even if you establish a valid connection with a DSN, the app itself, when it runs will for some reason open a pipe and pass the Login of the user no matter what. So any connection subsequently established from within the App will pass an NT4/5 type login, usually the user running the app. Unless the app itself explicitly describes what the UID and Pass should be. Again this can be counteracted in a trouble shooting mode by establishing that local account on the serving machine which matches the Login of the client machine.

 

[sledge0001]

No luck as of yet. I still feel that the problem is with me not linking the ODBC tables and the fox pro drivers correctly. I am not sure when I tyr to link the odbc files where should I be looking for the correct files . It also tells meonce and a while when I try to add the driver that I need to dowload it at http://msdn.microsfoft.com/vfoxpro/downloads. Of course this page does nopt exist! Damn you BILL GATES DAMN YOU!!! Would anyone out there be willing to help via the phone ?? I don't mind calling someone if they have the time..
You can email me @ chas@livesoundman.com or cboyer@niliconyc.com

 

[sledge0001]

Problems solved thanks to Sitka and bevancoleman as well as SQL. Thanks so much!
sledge0001