Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 6 of 6 total |
Adding TDBISAMSession produces error #11010 Table does not exist |
Wed, Oct 6 2010 1:10 PM | Permanent Link |
Barry | I am using DBISAM 4.26 locally and when I add a TDBISAM session to my TDBISAMDatabase and open a table, I get "DBISAM Engine Error #11010 Table or backup file 'CODES' does not exist".
The table opens fine if there is no TDBISAMSession component used. I ran a monitor and DBISAM is trying to open the table "E:\MyDocuments\Borland Studio Projects\Codes.Dat" instead of the table specified in the TDBISAMDatabase.Directory which is a DATA directory under the current program path. It doesn't matter if the table is opened in the IDE or at runtime. I still get 11010 error. Again, the error goes away if I don't use the TDBISAMSession. What gives? Barry BDS 2007 Win 7 |
Wed, Oct 6 2010 2:22 PM | Permanent Link |
Raul Team Elevate | Barry McClure wrote:
> I am using DBISAM 4.26 locally and when I add a TDBISAM session to my > TDBISAMDatabase and open a table, I get "DBISAM Engine Error #11010 > Table or backup file 'CODES' does not exist". > > The table opens fine if there is no TDBISAMSession component used. I > ran a monitor and DBISAM is trying to open the table > "E:\MyDocuments\Borland Studio Projects\Codes.Dat" instead of the > table specified in the TDBISAMDatabase.Directory which is a DATA > directory under the current program path. > > It doesn't matter if the table is opened in the IDE or at runtime. I > still get 11010 error. Again, the error goes away if I don't use the > TDBISAMSession. What gives? > How are you setting up the database directory? It works fine here (with 4.29.4) - adding/removing session. Even if there is no session component the default one is used so thre always is a session Raul |
Wed, Oct 6 2010 2:40 PM | Permanent Link |
Barry | Raul,
> How are you setting up the database directory? By hard coding the TDBISAMDatabase.Directory property in the object inspector. This works fine if there is no TDBISAMSession. As soon as I add a session component and have my TDBISAMDatabase.SessionName point to it, it tries to open the tables in MyDocuments folder for some reason. > It works fine here (with 4.29.4) - adding/removing session. > Even if there is no session component the default one is used so thre > always is a session True. But I am trying to switch to a TDBISAMSession so I can specify the PrivateDir to point to the Windows Temp directory, otherwise if I run the .exe over the network, it complains it can't create the temporary query results. Barry |
Wed, Oct 6 2010 3:00 PM | Permanent Link |
Raul Team Elevate | Barry McClure wrote:
> I add a session component and have my TDBISAMDatabase.SessionName > point to it, it tries to open the tables in MyDocuments folder for > some reason. Do you have DBISAMTable (or Query) objects linked to DBISAMDatabase ? if so are you updating the session on the database object only or for all of them. I was able to duplicate the error by having a DBISAMTable linked to DBISAMDatabase and having the table refer to default session while database was referring to my own session object. Raul |
Wed, Oct 6 2010 3:25 PM | Permanent Link |
Raul Team Elevate | Raul Sinimae wrote:
> Do you have DBISAMTable (or Query) objects linked to DBISAMDatabase ? > > if so are you updating the session on the database object only or for > all of them. > > I was able to duplicate the error by having a DBISAMTable linked to > DBISAMDatabase and having the table refer to default session while > database was referring to my own session object. > > Raul And if you create them in code then do you assign both databasename and sessionname or just databasename ? Raul |
Thu, Oct 7 2010 12:00 AM | Permanent Link |
Barry | "Raul Sinimae" wrote:
> Do you have DBISAMTable (or Query) objects linked to DBISAMDatabase ? > if so are you updating the session on the database object only or for > all of them. > I was able to duplicate the error by having a DBISAMTable linked to > DBISAMDatabase and having the table refer to default session while > database was referring to my own session object. Raul, you're right. I had to reassign the TDBISAMTable and TDBISAMQuery SessionNames for the components. Thanks for your help. Barry |
This web page was last updated on Thursday, March 28, 2024 at 06:05 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |