Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM ODBC Driver » View Thread |
Messages 1 to 5 of 5 total |
Connection issue & table does not exists |
Tue, Feb 12 2013 4:15 PM | Permanent Link |
Roeligan Roel Pauwels | Hi,
I'm trying to open an existing database. When making the connection with following connectionstring: DRIVER={DBISAM 4 ODBC Driver};ConnectionType=Local;CatalogName=ADM2013;Initial Catalog=C:\<<path>>\ADM2013 The connection seems to be opening fine but I keep getting the 11010 error 'table or backup file xxx does not exist' (xxx is the name of a dat file in the folder). When trying the connection using a preconfigured DSN I get following error when opening the connection: The specified DSN contains an architecture mismatch between the Driver and Application Any idea on what might be wrong or causing these issues? Thanks! |
Tue, Feb 12 2013 4:17 PM | Permanent Link |
Roeligan Roel Pauwels | Small update/note: using the evaluation ODBC driver for the moment (until I'm sure I can do the stuff needed...)
Roeligan wrote: Hi, I'm trying to open an existing database. When making the connection with following connectionstring: DRIVER={DBISAM 4 ODBC Driver};ConnectionType=Local;CatalogName=ADM2013;Initial Catalog=C:\<<path>>\ADM2013 The connection seems to be opening fine but I keep getting the 11010 error 'table or backup file xxx does not exist' (xxx is the name of a dat file in the folder). When trying the connection using a preconfigured DSN I get following error when opening the connection: The specified DSN contains an architecture mismatch between the Driver and Application Any idea on what might be wrong or causing these issues? Thanks! |
Wed, Feb 13 2013 3:51 AM | Permanent Link |
Chris Holland SEC Solutions Ltd. Team Elevate | Try changing the CatalogName to be the full path and it might be worth
adding a "PrivateDirectory" entry for a place where temporary tables can be stored as well. Chris Holland [Team Elevate] On 12/02/2013 21:15, Roeligan wrote: > Hi, > > I'm trying to open an existing database. > When making the connection with following connectionstring: > DRIVER={DBISAM 4 ODBC Driver};ConnectionType=Local;CatalogName=ADM2013;Initial Catalog=C:\<<path>>\ADM2013 > The connection seems to be opening fine but I keep getting the 11010 error 'table or backup file xxx does not exist' (xxx is the name of a dat file in the folder). > > When trying the connection using a preconfigured DSN I get following error when opening the connection: > The specified DSN contains an architecture mismatch between the Driver and Application > > Any idea on what might be wrong or causing these issues? > > Thanks! > |
Wed, Feb 13 2013 8:48 AM | Permanent Link |
Roeligan Roel Pauwels | Seems to work indeed... Thanks!!! R Chris Holland wrote: Try changing the CatalogName to be the full path and it might be worth adding a "PrivateDirectory" entry for a place where temporary tables can be stored as well. Chris Holland [Team Elevate] On 12/02/2013 21:15, Roeligan wrote: > Hi, > > I'm trying to open an existing database. > When making the connection with following connectionstring: > DRIVER={DBISAM 4 ODBC Driver};ConnectionType=Local;CatalogName=ADM2013;Initial Catalog=C:\<<path>>\ADM2013 > The connection seems to be opening fine but I keep getting the 11010 error 'table or backup file xxx does not exist' (xxx is the name of a dat file in the folder). > > When trying the connection using a preconfigured DSN I get following error when opening the connection: > The specified DSN contains an architecture mismatch between the Driver and Application > > Any idea on what might be wrong or causing these issues? > > Thanks! > |
Thu, Feb 14 2013 10:47 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Chris answered your other question, but I'll answer this one:
<< When trying the connection using a preconfigured DSN I get following error when opening the connection: The specified DSN contains an architecture mismatch between the Driver and Application >> This means that you're configuring the DSN for the 32-bit ODBC driver when using a 64-bit application, or vice-versa: http://www.elevatesoft.com/supportfaq?action=view&category=dbisam&question=odbc_driver_64_bit If you have any other questions, please let me know. Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Friday, April 19, 2024 at 07:09 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |