HELP ! - Runtime Error 216 at 0000309C

Discussion of open issues, suggestions and bugs regarding MyDAC (Data Access Components for MySQL) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
ScottTiger
Posts: 3
Joined: Sat 11 Feb 2006 12:32

HELP ! - Runtime Error 216 at 0000309C

Post by ScottTiger » Sat 11 Feb 2006 12:44

Hello to all,

I'm using myDac components with Delphi pro 5 + SP1 (Win XP pro + SP2), on a trial basis, before leaving BDE away.

I created a simple DB application with mySQL 5.0.1 and myDac 4.30.

The application works perfectly, but on a single point : on terminating, and only then, it generates the "Runtime Error 216 at 0000309C"

Please note :
- My PC & system are brand new ( < 1 month )
- I made sure the system is trojan-, virus- and spyware-free !

Any idea, anyone, please ?
Thanks for your attention.
Regards.

ScottTiger
Posts: 3
Joined: Sat 11 Feb 2006 12:32

Complement info for the CL team

Post by ScottTiger » Sat 11 Feb 2006 12:57

I've just found the following on info.borland.com :

[QC Short Description]
Using XPManfest + Groupbox in Dll form

[QC Description]
If you create an application that uses forms in a dll and the application has an xpmanifest and the dll form has a groupbox on it, you will get a runtime error 216 when the host application exits (but nothing when the dll form closes)

Note: You need to have the theme service enabled, and you also have to be using a Windows XP Visual Style, not the classic theme, to enable this:

QC Entry 4167
Any possible way to find a workaround ?

[email protected]
Posts: 3
Joined: Thu 18 Nov 2004 11:40

One solution...

Post by [email protected] » Sun 12 Feb 2006 17:56

Hi ALL,
I have the same problem...

SOLUTION:
I you close tables and queries using EVENT BeforeConnect, BeforeDisconnected, AfterConnect and AfterDisconnect of components TMYCONNECTION system will go out with the error runtime 216 EAccess Violation and so on... To Solve this remove any istruction in this events...

Seem a bug, I don't know...

ScottTiger
Posts: 3
Joined: Sat 11 Feb 2006 12:32

Post by ScottTiger » Sun 12 Feb 2006 23:36

Unfortunately, I didn't use any of these events.
For the test, I simply entered the DB login and password within the properties of the TMyConnection component.

I suppose we'll have to wait for a v.4.31 update. Hope the fix will explain what happened ...

:-)

Ikar
Posts: 1693
Joined: Thu 28 Oct 2004 13:56

Post by Ikar » Mon 13 Feb 2006 07:34

This is error of trial protection. Registered users have never informed us about similar problems.

Post Reply