Database Corrupted and compacting delete a Table with an error 1206

Using Delphi for developing, I get and delete records from an Access
Database 2000.

Sometimes, It happened 3 times (but not reproductible), the application did
not succeed in connecting the database. A table is corrupted and when you
compact, this table is deleted with an error -1206 created.

I did not find resources on this problem on the web. if somebody can help, I
have to solve it by Monday (it is quite HOT !).
If somebody can tell me what happened and maybe how to solve it or simply
what it is the turnaround, it will really help.

Thanx a lot !

julien

re: Database Corrupted and compacting delete a Table with an error 1206

Jucius wrote:
[color=blue]
> Using Delphi for developing, I get and delete records from an Access
> Database 2000.
>
> Sometimes, It happened 3 times (but not reproductible), the application did
> not succeed in connecting the database. A table is corrupted and when you
> compact, this table is deleted with an error -1206 created.[/color]

What is a 1206 error?

re: Database Corrupted and compacting delete a Table with an error 1206

"Salad" <oil@vinegar.com> a écrit dans le message de
news:400877CC.AF112055@vinegar.com...[color=blue]
> Jucius wrote:
>
>
> What is a 1206 error?
>[/color]

It is not documented. It seems to explain that a table is corrupted. Maybe
it is a problem with Long Values.

re: Database Corrupted and compacting delete a Table with an error 1206

Jucius wrote:
[color=blue]
> Using Delphi for developing, I get and delete records from an Access
> Database 2000.
>
> Sometimes, It happened 3 times (but not reproductible), the application did
> not succeed in connecting the database. A table is corrupted and when you
> compact, this table is deleted with an error -1206 created.[/color]

Well, a 1206 is undocumented per your post. Is 1206 a Delphi error? Or is it
an Access error.

When you connect to the database, do you have an error trap? I should think
that if you don't have an error trap, it would be hard to determine when the
error that corrups your table occurs. Somehow, someway, in Delphi you need to
errortrap your connection routine and even the delete routine.

re: Database Corrupted and compacting delete a Table with an error 1206

"Jucius" <zarbi_plus@hotmail.com> wrote:
[color=blue]
>Using Delphi for developing, I get and delete records from an Access
>Database 2000.
>
>Sometimes, It happened 3 times (but not reproductible), the application did
>not succeed in connecting the database. A table is corrupted and when you
>compact, this table is deleted with an error -1206 created.
>
>I did not find resources on this problem on the web. if somebody can help, I
>have to solve it by Monday (it is quite HOT !).[/color]

Is this on your own system? Or on a network with multiple users in your app?

If on a network then see the Access Corruption FAQ at my website for a wide variety
of reasons. I'd suggest the OpLocks fix first though.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

re: Database Corrupted and compacting delete a Table with an error 1206

"Salad" <oil@vinegar.com> a écrit dans le message de
news:4008BAC0.F836F9EC@vinegar.com...[color=blue]
> Jucius wrote:
>
> Well, a 1206 is undocumented per your post. Is 1206 a Delphi error? Or[/color]
is it[color=blue]
> an Access error.[/color]

1206 is the error I get when I try to repair the base. In fact, I compact
and I lost a table and get an error table that indicate an error 1206 (the
database cannot get the description of the table.
[color=blue]
> When you connect to the database, do you have an error trap? I should[/color]
think[color=blue]
> that if you don't have an error trap, it would be hard to determine when[/color]
the[color=blue]
> error that corrups your table occurs. Somehow, someway, in Delphi you[/color]
need to[color=blue]
> errortrap your connection routine and even the delete routine.[/color]

I did not succeed in connecting the database via ODBC.
The problem is that we did not succeed in reproducing the error from start
(when the table is OK)

Thanks,