Subject | Re: [IBO] Access Violation - Stored Procedure |
---|---|
Author | Paulo Henrique Albanez |
Post date | 2001-01-23T10:03:08Z |
I am also having a seemed problem.
To solve the same, I am having to use prepares and unprepare always.
The problem:
- Invalid Statement handle
- Invalid transation handle
- Access violation in the address 40561CBC the module 'GDS32.DLL'.
- Invalid request handle
The most strange is that when I access the base locally, the program works
perfectly.
If I use the UnPrepare method at procedures, the problem also disappears.
Does anybody have any ideas about the reason of this problem?
Would it be a problem with IBO?
I´m using:
Interbase 6.01 Super Server
Servidor Linux Conectiva 5.2
Windows 98 SE
Delphi 5.0
IBO 3.6Cd
PHA
To solve the same, I am having to use prepares and unprepare always.
The problem:
- Invalid Statement handle
- Invalid transation handle
- Access violation in the address 40561CBC the module 'GDS32.DLL'.
- Invalid request handle
The most strange is that when I access the base locally, the program works
perfectly.
If I use the UnPrepare method at procedures, the problem also disappears.
Does anybody have any ideas about the reason of this problem?
Would it be a problem with IBO?
I´m using:
Interbase 6.01 Super Server
Servidor Linux Conectiva 5.2
Windows 98 SE
Delphi 5.0
IBO 3.6Cd
PHA
----- Original Message -----
From: Dale Tabbert <dale@...>
To: <IBObjects@egroups.com>
Sent: Monday, January 22, 2001 5:11 PM
Subject: [IBO] Access Violation
> Hello,
>
> I have a stored procedure that enters values into a couple of
> tables. If I call it once and reboot the server everything is fine.
> If I call it twice in a row without rebooting I get:
>
> "Access Violation at address 40560C6F in module 'gds32.dll'. Read
> address 202020"
>
> Since this DB isn't in production yet, (but we would like it to be by
> the end of the week) we have just been recreating the DB from scratch
> each time we have changes. About two versions ago, I had this
> problem. We just moved the DB to a different box and all went well.
> Now with this build we have the same issue.
>
> Does anyone know what may have caused it?
> It doesn't happen in isql. I am using IB 6.01, IBO 3.6Ca
>
>
>
> TIA,
>
> Dale
>
>
>
>
>
>