I follow the instruction in the help file and
  manual in deploying dbexpress application.
  Every time I use dbexpint.dcu and midaslib.dcu
  and crtl, my app would get all sorts of access
  violation.  Removing it out solves the problem.
  Do I suppose to use these units to avoid all those require dlls ? Any help
appreciated.

  Jirayu

You might like to provide an example that demonstrates the problem. Please
make sure the example is complete and compilable.

--
Dave Nottage (TeamB)

Thanks for posting this. I had the same problem, and when I switched to
.dlls the problem went away. Yes, there is clearly a bug in the .dcus. I'm
using MySQL, not Interbase as you are, so my best guess is that the problem
is in midas or crtl.

I have same problem when include dbexpint.dcu and crtl.dcu (Delphi 6.02
Interbase 6)
After using TSQLQuery with this statment:
  EXECUTE PROCEDURE UPDATE_PRICE(:FromCity, :ToCity, :Price , :IsPackage);
ExecSQL work Ok all data changed but when  form destroing I receive access
violation in this place:

destructor TCustomSQLDataSet.Destroy;
begin
  Close;
  if Assigned(FSQLCursor) then FreeCursor;
==>  if Assigned(FSQLCommand) then FreeStatement;
  FreeAndNil(FParams);
  FreeAndNil(FIndexDefs);
  SetConnection(nil);
  FreeProcParams(FProcParams);
  inherited Destroy;
  FDataLink.Free;
  FreeBuffers;
end;

"Nickolai Kornachenko" <nkornache...@tut.by>

yeah, I confirm this one...

The dbexpint dcu to be linked statically in the app is definitely broken, if
compared with dbexpint.dll.

3 out of 12 bugs concerning Dbexpress now reported in Quality Central are
relative to statically linked Dbexpress (#330, #377, #1452)

"Marco Dugoni" <marco dot dug...@gsmbox.it> wrote:

I had exactly same problem when included dbexpora.dcu and crtl.dcu (Delphi 6.02 Oracle 8.1.7).

In my case it was a TSQLDataSet with
   CommandType := ctQuery;
   CommandText := 'begin COMMISSION.PRC_UPDATE_AGENT(:V_AG_NUMBER,:V_AG_NAME,:V_AG_BRANCH); end;'.

ExecSQL worked properly, but TCustomSQLDataSet.Destroy raised an access violation.

My temporarily solution was to exclude dbExpOra and Crtl from uses clause and to deliver
application in package consisting of the application executable and the dbexpora.dll.