Hi everybody,

I have a Problem at a customer, and only there (Delphi 7, DBISAM local)

The Customer gets an eDBISAMEngineError #11013, Acces denied to Table or
Backup File ProjektParam.dat .. at the following action:

Query.sql.Clear;
Query.sql.Add('ALTER TABLE ProjektParam ADD '+pp.FieldName+' CHAR(50)');
Query.ExecSQL;

The table is not write protected and there are sufficient user rights in the
network. Also his Temp directory settings are OK. I have already let him
make test with a small test program that does only the above action to
elimiate side effects of my application.
He also already copied the database to a local path on his machine,
everything is useless, always the same error.

And the problem occurs only at this customer, not on my computer ant not at
other customers.

Any ideas where to look?

Regards
Burkhard Schneider

Burkhard


Corrupt table?

Roy Lambert

"Roy Lambert" schrieb

> Burkhard
>
>
> Corrupt table?
>
> Roy Lambert
>

No, I've checked that.

Burkhard Schneider

Burkhard

> The Customer gets an eDBISAMEngineError #11013, Acces denied to Table or
> Backup File ProjektParam.dat .. at the following action:
>
> Query.sql.Clear;
> Query.sql.Add('ALTER TABLE ProjektParam ADD '+pp.FieldName+' CHAR(50)');
> Query.ExecSQL;

This look like another process in this computer (or other) is using this
table and there DBISAM raise this error.
To perform an "alter table" SQL statement, you must exclusive access to this
table.

Eduardo

"Burkhard Schneider" <info@burkhard-schneider.de> wrote in message
news:4E62FD8A-A829-4F36-9C1D-84EBFBF27F4D@news.elevatesoft.com...
> Hi everybody,
>
> I have a Problem at a customer, and only there (Delphi 7, DBISAM local)
>
> The Customer gets an eDBISAMEngineError #11013, Acces denied to Table or
> Backup File ProjektParam.dat .. at the following action:
>
> Query.sql.Clear;
> Query.sql.Add('ALTER TABLE ProjektParam ADD '+pp.FieldName+' CHAR(50)');
> Query.ExecSQL;
>
> The table is not write protected and there are sufficient user rights in
> the network. Also his Temp directory settings are OK. I have already let
> him make test with a small test program that does only the above action to
> elimiate side effects of my application.
> He also already copied the database to a local path on his machine,
> everything is useless, always the same error.
>
> And the problem occurs only at this customer, not on my computer ant not
> at other customers.
>

It seems to be  related to the session temporary directory.

http://www.elevatesoft.com/bulletin_9.htm

Easy to test if this is the case. Do a rename (using explorer) and then
rename the table and the index back to their original names, problem goes
away.

Since you already have determined that the temp directory is OK, make sure
all tables and queries have the right session, etc. But it for sure sounds
like this problem, which started with XT.

If this does not help, do a search in Elevate incident report with 11013.

Robert

An antivirus program will of course cause these types of errors too.
Disable scanning your DB directory or omit the extension types if you
haven't already tried this.

Donat.

>
> The Customer gets an eDBISAMEngineError #11013, Acces denied to Table or
> Backup File ProjektParam.dat .. at the following action:
>

Burkhard,

<< The table is not write protected and there are sufficient user rights in
the network. Also his Temp directory settings are OK. I have already let him
make test with a small test program that does only the above action to
elimiate side effects of my application.He also already copied the database
to a local path on his machine, everything is useless, always the same
error. >>

More than likely the issue is what Robert or Donat pointed out - an XP file
rights issue or an issue with some AV software.  These are the two most
likely culprits:

http://www.elevatesoft.com/bulletin_9.htm
http://www.elevatesoft.com/bulletin_14.htm

--
Tim Young
Elevate Software
www.elevatesoft.com

"Robert" schrieb:
>
> It seems to be  related to the session temporary directory.
>
> http://www.elevatesoft.com/bulletin_9.htm
>

Hi Robert and the others,

thank you, it was the temp directory problem.

I even already used Engine.CreateTempTablesInDatabase but it seems that I
put this statement at a wrong place, where the engine already was active so
it had no effect.

regards
Burkhard Schneider

Burkhard,

<< I even already used Engine.CreateTempTablesInDatabase but it seems that I
put this statement at a wrong place, where the engine already was active so
it had no effect. >>

Thanks for the update - I'm glad that you've got it working okay now.

--
Tim Young
Elevate Software
www.elevatesoft.com