Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread Error 11013 creating tables via sql, following mkdir
Wed, Feb 1 2006 10:01 PMPermanent Link

Dave M
I am getting Error 11013 trying to create tables via sql.

This only happens if the program creates a fresh directory (via mkdir) and then the query
tries to create the table in the new directory.  This is WinXp home, no antivirus active.

Following the program abend, the program can be restarted.  The query can then use the
directory created from the previous execution.

The current process isn't able to use the directory without a restart.

Anyone familiar with this?  


Dave M
Wed, Feb 1 2006 10:12 PMPermanent Link

Dave M
Dave M <mr_mensch2@hotmail.com> wrote:

The current process isn't able to use the directory without a restart.
-------------------------------------------------------------------------------------------------

To clarify this, it is possible for the program to copy a file to the new directory
immediately, before restart.  It is the
the DBISAMQuery that reports the error.  


Dave M
Thu, Feb 2 2006 1:25 AMPermanent Link

"Clive"
Do you close your TDBISAMDatabase then change the path and reopen prior to
SQL exec?

"Dave M" <mr_mensch2@hotmail.com> wrote in message
news:24EB745A-6FEE-4FEF-A7DD-8678CADC446D@news.elevatesoft.com...
> Dave M <mr_mensch2@hotmail.com> wrote:
>
> The current process isn't able to use the directory without a restart.
> -------------------------------------------------------------------------------------------------
>
> To clarify this, it is possible for the program to copy a file to the new
> directory
> immediately, before restart.  It is the
> the DBISAMQuery that reports the error.
>
>
> Dave M
>

Thu, Feb 2 2006 2:42 AMPermanent Link

Dave M
"Clive" <dd@dddd.com> wrote:

Do you close your TDBISAMDatabase then change the path and reopen prior to
SQL exec?
-------------------------------------------------------------------------------------------

Good suggestion. The program is doing an initial install.  The path is set before the sql
execution.  
The mistake was having the database connected before creating the directory.
This means connected to a non existent db. (No error message at this point.)
By setting connected after the directory creation, the error goes away.

Dave M


Image