Every once in a while I get this 11010 error. In my case I used the copy table method to create a new table for my C/S project using the DBSYS utility. I noticed that backup table is not created until a new record or transaction is done on the new table set from within the utility.  This was my first incident that took me for a loop as to why there was no backup table and error. I am using DBISAM 4.37 build 3 under D7.

Once the table set was complete I still got the error while trying to build my project. After checking my table name properties I was bewildered why the 11010 error.  This was because I had simply forgot to enter the session name on the new table component. Once I entered the session name all was OK.

Hope this helps prevent some frustration for others.  Just wondering if an exception can be added if the table session name is left blank somehow.

John P.

On 2/25/2014 2:38 PM, John Postnikoff wrote:
> In my case I used the copy table method to create a new table for my C/S project using the DBSYS utility. I noticed that backup table is not created until a new record or transaction is done on the new table set from within the utility.

Not seeing it here - dbsys table copy copies the file (both for local
and remote session) and table files (dat/idx in my case) show up in
destination right away (no need to add record or such).

Can you clarify the steps you're doing? DBSYS is not delphi dependent so
we should be seeing same thing.


> Once the table set was complete I still got the error while trying to build my project. After checking my table name properties I was bewildered why the 11010 error.  This was because I had simply forgot to enter the session name on the new table component. Once I entered the session name all was OK.

You mean error when doing a delphi build?!

SessionName is not a required property and when blank default session is
used (which is a local session auto-created by dbisam). This means that
for most people using db/tables things "just work" without having to
even add a session object so no error should be raised.

Raul

On 2/26/2014 10:35 AM, Raul wrote:
> On 2/25/2014 2:38 PM, John Postnikoff wrote:
>> In my case I used the copy table method to create a new table for my
>> C/S project using the DBSYS utility. I noticed that backup table is
>> not created until a new record or transaction is done on the new table
>> set from within the utility.
>
> Not seeing it here - dbsys table copy copies the file (both for local
> and remote session) and table files (dat/idx in my case) show up in
> destination right away (no need to add record or such).

Nevermind - i misread the question.  However answer is still not seeing
it here.

Adding a record to copied table does not (and should not) result in a
backup copy of the table. Backup is only made when you alter the table
(or repair op or such).

Raul

Hi Raul,

What I may be trying to say is the .dbk file or *bk backup files are not automatically created, this causing the error as they do not exist.

John


Raul wrote:

On 2/26/2014 10:35 AM, Raul wrote:
> On 2/25/2014 2:38 PM, John Postnikoff wrote:
>> In my case I used the copy table method to create a new table for my
>> C/S project using the DBSYS utility. I noticed that backup table is
>> not created until a new record or transaction is done on the new table
>> set from within the utility.
>
> Not seeing it here - dbsys table copy copies the file (both for local
> and remote session) and table files (dat/idx in my case) show up in
> destination right away (no need to add record or such).

Nevermind - i misread the question.  However answer is still not seeing
it here.

Adding a record to copied table does not (and should not) result in a
backup copy of the table. Backup is only made when you alter the table
(or repair op or such).

Raul

<<John Postnikoff wrote:

What I may be trying to say is the .dbk file or *bk backup files are not automatically created, this causing the error as they do not exist.
>>

Ok but what i'm saying is that if you copy the table and then add some records to it the backup files should not get created at all. Backup files are created only when you alter/optimize/repair the tables which you're not doing in this case. So if you're getting a backup table created just by adding a record then your code must be doing something more.

Also as far as i know the backup tables are just that - backup tables -  and not used by dbisam so you should not be getting the error 11010 with backup tables.

Maybe if you want to post the steps and what you see it would help

Raul