Re: CommonDialog returns wrong context
- From: "Ken Halter" <Ken_Halter@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 24 Jan 2007 14:50:25 -0800
"nb0512" <nb0512@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DE8769A4-7FBF-460A-A5BF-A6388CEF4135@xxxxxxxxxxxxxxxx
Should I really take all Adodc controls out and replace them with code ?
Is
that my only option ? Couldn't I also set the connectionstrings to some
dummy
database at design time using an absolute path (to satisfy the Adodc's
while
initializing) and then in the form load procedure, change the
connectionstring to the App.Path ? This would mean 'only' one copy of the
database (could even be empty).
Thanks
nb0512
Have you tried loading those controls at runtime? That should eliminate any
"out of order" events that may be firing.... that should give you full
control over a forms or variables properties before the control even exists.
--
Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
In Loving Memory - http://www.vbsight.com/Remembrance.htm
.
- Follow-Ups:
- Re: CommonDialog returns wrong context
- From: Ken Halter
- Re: CommonDialog returns wrong context
- References:
- Re: CommonDialog returns wrong context
- From: MikeD
- Re: CommonDialog returns wrong context
- From: nb0512
- Re: CommonDialog returns wrong context
- From: nb0512
- Re: CommonDialog returns wrong context
- Prev by Date: Re: CommonDialog returns wrong context
- Next by Date: Re: CommonDialog returns wrong context
- Previous by thread: Re: CommonDialog returns wrong context
- Next by thread: Re: CommonDialog returns wrong context
- Index(es):
Relevant Pages
|