Subject | RE: [IBO] Access Violation, Error in FPXSQLVAR.aliasname_length |
---|---|
Author | Jason Wharton |
Post date | 2004-07-23T20:36:52Z |
In this case you possibly have an incorrect version of GDS32.dll on your
client or perhaps your package files are not in sync with your DCU's.
Perhaps you can continue to dig for more clues. So far I don't know what
more to suggest.
Jason Wharton
-----Original Message-----
From: jaguarius2003 [mailto:jaguarius@...]
Sent: Thursday, July 22, 2004 2:40 PM
To: IBObjects@yahoogroups.com
Subject: RE: [IBO] Access Violation, Error in FPXSQLVAR.aliasname_length
I moved the code and it didn't change anything. Now would be a good
time to mention that, this is also happening on a form that does not
close when post is pressed. I have a pagecontrol on a form with a set
of TAction based update buttons whic generates the same cannot focus a
disabled or invisible window error.
I am inclined to think that you are on the wrong track about the on
close event - the other form does the exact same thing just from
pressing post.
Jason S. Gagnon
after an >>exception is
client or perhaps your package files are not in sync with your DCU's.
Perhaps you can continue to dig for more clues. So far I don't know what
more to suggest.
Jason Wharton
-----Original Message-----
From: jaguarius2003 [mailto:jaguarius@...]
Sent: Thursday, July 22, 2004 2:40 PM
To: IBObjects@yahoogroups.com
Subject: RE: [IBO] Access Violation, Error in FPXSQLVAR.aliasname_length
I moved the code and it didn't change anything. Now would be a good
time to mention that, this is also happening on a form that does not
close when post is pressed. I have a pagecontrol on a form with a set
of TAction based update buttons whic generates the same cannot focus a
disabled or invisible window error.
I am inclined to think that you are on the wrong track about the on
close event - the other form does the exact same thing just from
pressing post.
Jason S. Gagnon
>>Do this in the OnCloseQuery event rather than the OnClose event. Byexception >>to immediately re-raise it and then have a line of code
>>the time
>>it gets to OnClose, the form is indeed closing already.
>>Also, your Delphi code doesn't make any sense. Why catch an
after an >>exception is
>>raised? Your call to Abort will never happen.
>>Jason Wharton