Re: ADO in MDI Apps
- From: "Christopher P Galang" <spiderwaui@xxxxxxxxxxx>
- Date: Fri, 22 Apr 2005 13:46:38 +0800
My friend,
Maybe your MDI form is not automatically created when your exe file loads.
If you do use a application.createform in runtime, chances are you get AV
message. another thing is, this AV are somewhat rare but if this happen. DO
NOT ,i say. DO NOT cut and paste your ADO comps from one form to another.
create a new one and most likely create a new form and add this ADO comps of
yours. Try it, if it works, well, I think this kind of procedure sucks
Delphi! what if you have already finished your forms design and it has lots
of Controls in it. (OUCH!). Its a bug found in ver6 upto ver7 of Delphi.
Don't know why borland does not look into this matter.
BTW i'm using Windows XP Prof. SP2.
"Jeremy Collins" <jd.collins@xxxxxxxxxxxxxxxx> wrote in message
news:4263ae36$2@xxxxxxxxxxxxxxxxxxxxxxxxx
> Dexter wrote:
> > Okay this is probably a realy dumb question but, I'm trying to access an
> > access database from within an MDI child window using the standard ADO
comps
> > that come with Delphi 7, the problem is each time I try to access any of
the
> > compenents methods I get an access violation. I've also tried moving
the
> > ADO components from the child to the parent form but again, I get access
> > violations when for example I try to move from one field to the next in
a
> > record set. Is it possible to get the MDI child windows to talk the
> > database properly & how???
>
> It is utterly impossible to answer this question. Show us the code
> that causes the AV.
>
>
>
> --
> jc
>
> Remove the -not from email
.
- References:
- ADO in MDI Apps
- From: Dexter
- Re: ADO in MDI Apps
- From: Jeremy Collins
- ADO in MDI Apps
- Prev by Date: Re: ADO Deployment
- Next by Date: master/detail using access db.
- Previous by thread: Re: ADO in MDI Apps
- Next by thread: Re: ADO in MDI Apps
- Index(es):
Relevant Pages
|
