I am using the ODBC driver with Access to connect to a database (note remote, local with just a path). I am running VIsta and Office 2007. When
I just install the driver and create the ODBC connection, I am able to open the tables but I soon I close Access and reopen it, it gives me that
error (look at the attchment).

If I uninstall and reinstall, then I am able to read the table again but only once.

Thanks.

Danielle

Danielle,

<< I am using the ODBC driver with Access to connect to a database (note
remote, local with just a path). I am running VIsta and Office 2007. When I
just install the driver and create the ODBC connection, I am able to open
the tables but I soon I close Access and reopen it, it gives me that error
(look at the attchment). >>

What version of the DBISAM ODBC Driver are you using ?

--
Tim Young
Elevate Software
www.elevatesoft.com

I am using 4.26.

Danielle

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Danielle,

<< I am using the ODBC driver with Access to connect to a database (note
remote, local with just a path). I am running VIsta and Office 2007. When I
just install the driver and create the ODBC connection, I am able to open
the tables but I soon I close Access and reopen it, it gives me that error
(look at the attchment). >>

What version of the DBISAM ODBC Driver are you using ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Danielle,

<< I am using 4.26. >>

What is the path that you're using for the database catalog setting in the
DSN, and what is the path being used for the private directory setting in
the DSN ?  If they're very long, this can cause Access to screw them up
because it uses a fixed-length buffer of 512 bytes for the entire connection
string.  Don't ask me why, in 2008, that this is still the case.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

I was using the same path before with Windows XP and it worked fine. I have attached a file with all my odbc configuration options. If I recreate
the odbc config, it works until I close Access and reopen it again.

I did a test: I created a new odbc connection with the read only driver and it works fine!!??

Thanks.

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Danielle,

<< I am using 4.26. >>

What is the path that you're using for the database catalog setting in the
DSN, and what is the path being used for the private directory setting in
the DSN ?  If they're very long, this can cause Access to screw them up
because it uses a fixed-length buffer of 512 bytes for the entire connection
string.  Don't ask me why, in 2008, that this is still the case.

--
Tim Young
Elevate Software
www.elevatesoft.com

Danielle,

<< I was using the same path before with Windows XP and it worked fine. I
have attached a file with all my odbc configuration options. If I recreate
the odbc config, it works until I close Access and reopen it again. >>

Are you using Vista ?  If so, are you creating the path anywhere in the
Program Files directory or subdirectories ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Yes, I am using Vista. The path to the database is not in Program Files but the program is installed there. The temp file goes to the directory users.

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Danielle,

<< I was using the same path before with Windows XP and it worked fine. I
have attached a file with all my odbc configuration options. If I recreate
the odbc config, it works until I close Access and reopen it again. >>

Are you using Vista ?  If so, are you creating the path anywhere in the
Program Files directory or subdirectories ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Danielle,

<< Yes, I am using Vista. The path to the database is not in Program Files
but the program is installed there. The temp file goes to the directory
users. >>

By "program" do you mean the DBISAM ODBC Driver, some other program, or
Access ?  Also, are you using a system DSN or user DSN for the ODBC
connection ?

If you could send me via email the registry settings that you have for the
DSN, it would help.  You can find them here in the registry:

System DSN

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI

User DSN

HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI

Just use RegEdit, find your DSN name under that key, and then right-click on
the DSN and select Export to create the file.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Danielle,

<< Yes, I am using Vista. The path to the database is not in Program Files
but the program is installed there. The temp file goes to the directory
users. >>

By "program" do you mean the DBISAM ODBC Driver, some other program, or
Access ?  Also, are you using a system DSN or user DSN for the ODBC
connection ?

If you could send me via email the registry settings that you have for the
DSN, it would help.  You can find them here in the registry:

System DSN

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI

User DSN

HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI

Just use RegEdit, find your DSN name under that key, and then right-click on
the DSN and select Export to create the file.

--
Tim Young
Elevate Software
www.elevatesoft.com

Danielle,

Thanks, the registry settings look okay, although they will be virtualized
per-user under Vista because they're part of the HKEY_LOCAL_MACHINE hive.

Where is the Access database that you're using for linking the tables
located ?

--
Tim Young
Elevate Software
www.elevatesoft.com