Problem with MDB database connection

what if you run it outside of the IDE? same error? if so, can you do a step by step debugging and see exactly which line from your code makes the error fire up? For faster pinpoint of teh place, use at first only step over. after error, you will now the line and then at that line do a step in, and again step over until error. and so on until you find the line with problem.
alternativly, you can use your intuition :)

Put this line back in your project *.DPR file:

  Application.Initialize;

When your application uses the COM units, this single line will initialize the whole COM services for your application. It should be executed before you try any other COM call.

Thanks for the replies guys...

JDskinner - nope that did nothing...
ciuly -  i did use a step through, and the problem came up as i showed in the first post :P
Workshop_alex - im not sure what you mean, but wouldnt that make the exe bigger...

Geobul your spot, on ... !

Solution : *.dpr file

uses
  Forms,
  ActiveX,
  windows,
  Unit1 in 'Unit1.pas' {Form1},
  Unit2 in 'Unit2.pas' {Form2},
  Unit3 in 'Unit3.pas' {Form3};

{$R *.RES}

begin
  CoInitialize(nil);
  try
  Application.Title := 'Test Run';
  Application.CreateForm(TForm1, Form1);
  Application.CreateForm(TForm3, Form3);
  Application.CreateForm(TForm2, Form2);
  Application.Run;
  finally
    CoUninitialize;
  end;
end.

Thanks again :P

Peace Gav

Hi,

I agree with Alex. You should initialize your app object because you never know (well, I, at least :-) which unit, either called directly or indirectly by another unit you're using, sets InitProc of the app. It is ComObj in your case used by DB and AdoDB units but there might be others also.

Regards, Geo

Alex, after some research... you are right...

Im going to ask that the question be reopened and that both you and Geobul get the points
Id also like to thank the both of you for the response and the somewhat detailed solutions.

The workaround as you call it, was my first choice cause i needed a solution fast for this project, but after i finished it and had time to look over it again, ...well i saw the bigger picture :P

Peace Gav

Thanks. :-)

A lot of programmers tend to remove that Initialize line because they think it doesn't do anything or because of other reasons. (For example: my application becomes bloated if I use it.) But the Delphi VCL uses it for some special units which require additional initialization when the application starts.

Geo's solution is the one you should use when e.g. writing console applications thus very useful to know about. And basically it does work. :-)

Hi,

It is a proper decision to split the points, Scay7. I'm on my summer vacation now and that Application.Initialize thing didn't come in my mind as a correct answer at all ;-) Perhaps because I've never removed that line but had similar problems with other non-standard types of applications and that was the only solution I've found.

Regards, Geo