Posted before but didnt get help yet...Trying this another way...
I have a VB 6.0 app using access 2003 database. This app resynchs their laptops to the master database on a machine in their office.. They use when they leave the office to copy the dbase locally to the laptop and then point the odbc connection for the app to the copied database... c:\... instead of s:\..
They then use another vb app which writes to the dbase locally...
Upon return to the office they then resynch the master dbase on the machine in their office... Update with changes made while in the field....
All worked fine until VISTA... I had to install Office 2007 with access on two newly purchased laptops.( Another story)
I had everything running fine until Last week. I now get an error trying to run the "Go remote" utility
Microsoft[ODBC Microsoft Access Driver] 'Unknown' is not a valid path. Make sure the path name is spelled correctly and that you are connected to the server....
-2147467259(80004005)..
I have googled and read alot and tried a lot of things.. rebooting all machines hasnt worked. Permissions havent changed since it was working ok.. If I try and debugg it in VStudio 2000 It works fine???? Any ideas??
After having to remove almost all of Vista's Security features I finally recompiled the app on the vista machine and it(the exe) came up OK. However I started getting permission errors. First it comes up and says it cant find the table. I then open the mdb file in access and then close the database without making any changes. I then rerun the app and get an error from the exe stating I dont have permission to read the tables.. HUH???? Is their something to do with the way vista lets the machine open up an mdb file? I went into the security in access and gave all users admiin authority on all tables and I got it to work on one machine three times in a row. I then went to the other laptop and tried to pull up the new exe and immediately got the same error I received before on both machines. The other machine that was working, then would error out again with a permission error. Arghh!!
I have a VB 6.0 app using access 2003 database. This app resynchs their laptops to the master database on a machine in their office.. They use when they leave the office to copy the dbase locally to the laptop and then point the odbc connection for the app to the copied database... c:\... instead of s:\..
They then use another vb app which writes to the dbase locally...
Upon return to the office they then resynch the master dbase on the machine in their office... Update with changes made while in the field....
All worked fine until VISTA... I had to install Office 2007 with access on two newly purchased laptops.( Another story)
I had everything running fine until Last week. I now get an error trying to run the "Go remote" utility
Microsoft[ODBC Microsoft Access Driver] 'Unknown' is not a valid path. Make sure the path name is spelled correctly and that you are connected to the server....
-2147467259(80004005)..
I have googled and read alot and tried a lot of things.. rebooting all machines hasnt worked. Permissions havent changed since it was working ok.. If I try and debugg it in VStudio 2000 It works fine???? Any ideas??
After having to remove almost all of Vista's Security features I finally recompiled the app on the vista machine and it(the exe) came up OK. However I started getting permission errors. First it comes up and says it cant find the table. I then open the mdb file in access and then close the database without making any changes. I then rerun the app and get an error from the exe stating I dont have permission to read the tables.. HUH???? Is their something to do with the way vista lets the machine open up an mdb file? I went into the security in access and gave all users admiin authority on all tables and I got it to work on one machine three times in a row. I then went to the other laptop and tried to pull up the new exe and immediately got the same error I received before on both machines. The other machine that was working, then would error out again with a permission error. Arghh!!
