Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread ISAPI problem using INSERT INTO under IIS 5.1
Tue, Jul 11 2006 11:33 AMPermanent Link

"Steve McGrath"
Hi,

I'm not sure if I should be asking this in the kbmMW or DBISAM groups but
here goes:
I'm accessing a DBISAM database emdedded in a ISAPI dll using kbmMW.
I've got my ISAPI running fine using Kims Masden's wwwserver.exe ( a
standalone web server ideal fro debugging). I can happily run select and
insert queries.
I now have to move to IIS and the select queries are working but if I try to
execute an INSERT query I get the following error "Error creating table
handle (100000)". I can insert with no difficulties using wwwserver.exe.
In IIS I have verified all permissions and the fact that I can run Select
queries would indicate that the running of scripts and executbales is
configured correctly. Also the folders are stored on a FAT32 partition so
directory permissions should not be required. I also set the
DBISAMDatabase.PrivateDir property to a folder on the FAT32 partition but to
no avail. Does DBISAM do anything different using INSERT statements?
Has anyone encounterd this type of problem??

Thanks,
Steve

Tue, Jul 11 2006 2:18 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Steve,

<< I now have to move to IIS and the select queries are working but if I try
to execute an INSERT query I get the following error "Error creating table
handle (100000)". >>

Make sure that you're calling the TDBISAMQuery.ExecSQL method and not the
Open method if you're using 3.x or earlier and running a non-SELECT query.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Jul 11 2006 3:11 PMPermanent Link

Steve McGrath
Tim Young [Elevate Software] wrote:
> Steve,
>
> << I now have to move to IIS and the select queries are working but if I try
> to execute an INSERT query I get the following error "Error creating table
> handle (100000)". >>
>
> Make sure that you're calling the TDBISAMQuery.ExecSQL method and not the
> Open method if you're using 3.x or earlier and running a non-SELECT query.
>

Tim,

I use the Execute method to run the query. The fact that it runs Ok
under one type webserver seems to prove that the coding isn't too far
off the mark. My setup would be a kbmMW client talking to a serverside
kbmMWDBISAMQuery component in the ISAPI where I also have the DBISAM
database and session - both v4. The database folder is a subfolder of
where the dll is located.
The difference between the working and non-working setup is that the
standalone exe webserver is running  under my credentials (local
administrator) whereas IIS is running as a service and also uses the
IUSR_machinename account.
To drill down further to the problem, it is only an issue when inserting
a record (again a serverside query called remotely from the client). So
now we're writing somewhere - does DBISAM do anything different outside
of its own directory when calling INSERT? I don't have COM initialised
in my DataModule - could this be a factor with IIS?

Thanks,
Steve
Wed, Jul 12 2006 4:26 AMPermanent Link

Steve McGrath
Tim Young [Elevate Software] wrote:
> Steve,
>
> << I now have to move to IIS and the select queries are working but if I try
> to execute an INSERT query I get the following error "Error creating table
> handle (100000)". >>
>
> Make sure that you're calling the TDBISAMQuery.ExecSQL method and not the
> Open method if you're using 3.x or earlier and running a non-SELECT query.
>

Tim,

further investigation showed the problem only occurred when I called a
server side query to do the INSERT. Client side INSERT SQL worked fine.
I then started looking at the properties of the kbmMWDBISM4Query and
there is a property called AutoFieldDefsOnOpen which needed to be
changed from its default value to mwafoNever and now the server side
query works fine.
The problem was in no way related to DBISAM but to some quirk of IIS and
the above kbmMW component property.

Thanks,
Steve
Wed, Jul 12 2006 2:13 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Steve,

<< further investigation showed the problem only occurred when I called a
server side query to do the INSERT. Client side INSERT SQL worked fine. I
then started looking at the properties of the kbmMWDBISM4Query and there is
a property called AutoFieldDefsOnOpen which needed to be changed from its
default value to mwafoNever and now the server side query works fine.  The
problem was in no way related to DBISAM but to some quirk of IIS and the
above kbmMW component property. >>

Thanks for sharing, though.  That's what makes these newsgroups valuable.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image