[AccessD] Yes. Another Silly Access Question.

That is exactly the case.

On another note.  I have it pulling a single record
like I want.  What a pain....hehehe

My problem now is, that it gives me a "unable to lock
table" blah bla when I call it from my main form via a
command button due to the table being used by a
subform.

Is there a way I can temporarily disable the subform
while the code behind the button is doing it's work so
I can remedy this error?

--- John Bartow <john at winhaven.net> wrote:
> Dittos here. However in Frank's Case it sounds like
> he has somebody looking
> into the app. to see how its done rather what the
> results.
> 
> JB
> "Control freaks "freak" me out!"
> 
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com]On
> Behalf Of Charlotte
> > Foust
> > Sent: Wednesday, October 29, 2003 10:54 AM
> > To: Access Developers discussion and problem
> solving
> > Subject: RE: [AccessD] Yes. Another Silly Access
> Question.
> >
> >
> > That's the approach I use as well, Drew.  I give
> them the result they're
> > looking for and hide the details so they don't
> realize I did it right
> > instead of the way they wanted it done.
> >
> > Charlotte Foust
> >
> 
> 
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com