Hi
I was wondering if anyone could explain this error to me.
Dbisam DBEngline Error #11010 backup table\ dbisam.lck does not exist. When I look in the directory the dbsiam.lck does exists.
Also what is strange is that if I use this same exact code with a different table,it works. When I try it with anothe table that is exactly the same
(except for the data), it doesn't work. I have used this code for over a year and it has worked up unitl now. I haven't made any changes that I
know of.

Thanks for your help
If any more additonal info is needed, I will be happy to post it
THanks
K

Kara,

<< I was wondering if anyone could explain this error to me.
Dbisam DBEngline Error #11010 backup table\ dbisam.lck does not exist. When
I look in the directory the dbsiam.lck does exists.
Also what is strange is that if I use this same exact code with a different
table,it works. When I try it with anothe table that is exactly the same
(except for the data), it doesn't work. I have used this code for over a
year and it has worked up unitl now. I haven't made any changes that I know
of. >>

What is the database path for the table that you're trying to open ?  Is it
local on your PC, or is it on a network server ?  Try erasing the dbisam.lck
file and see if that fixes the problem.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,
I am running it on my local PC. Right before I get the error I am creating a set of tables so I am going try to delete the dbsiam.lnk file that is
already in that directory. The odd thing about it if that I use the same code and procedure to run the same tables and it works. The only difference
is the table I am selecting from. I also use the same code to create the dbisam table so the table shouldn't be the issue. Both times, I call the
procedure to create a tables, it should create the error but for some reason it only happens once. I also have blocked out all the code and just run
that one procedure and the error still appears. If I block out all the code and select from the other table (which has all the same fields and created
the same way as the other table) and the code works. It is very strange

Thanks for your help
Kara











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

Kara,

<< I was wondering if anyone could explain this error to me.
Dbisam DBEngline Error #11010 backup table\ dbisam.lck does not exist. When
I look in the directory the dbsiam.lck does exists.
Also what is strange is that if I use this same exact code with a different
table,it works. When I try it with anothe table that is exactly the same
(except for the data), it doesn't work. I have used this code for over a
year and it has worked up unitl now. I haven't made any changes that I know
of. >>

What is the database path for the table that you're trying to open ?  Is it
local on your PC, or is it on a network server ?  Try erasing the dbisam.lck
file and see if that fixes the problem.
--
Tim Young
Elevate Software
www.elevatesoft.com

Kara,

<< I am running it on my local PC. Right before I get the error I am
creating a set of tables so I am going try to delete the dbsiam.lnk file
that is already in that directory. The odd thing about it if that I use the
same code and procedure to run the same tables and it works. The only
difference is the table I am selecting from. I also use the same code to
create the dbisam table so the table shouldn't be the issue. Both times, I
call the procedure to create a tables, it should create the error but for
some reason it only happens once. I also have blocked out all the code and
just run that one procedure and the error still appears. If I block out all
the code and select from the other table (which has all the same fields and
created the same way as the other table) and the code works. It is very
strange >>

Are you using a TDBISAMDatabase component at all ?  If so, are you verifying
that the Directory setting in the TDBISAMDatabase component is valid and a
legitimate directory on the local computer ?  If you aren't using a
TDBISAMDatabase component, then the same holds true for the
TDBISAMTable.DatabaseName property - it must hold a valid path if it isn't
referring to a TDBISAMDatabase component's DatabaseName property.

--
Tim Young
Elevate Software
www.elevatesoft.com