you're welcome, Connie ;) happy to help
Warm Regards,
Crystal
*
(: have an awesome day :)
*
________________________________
From: mrsgoudge
Thanks for the heads up. I'll check it out
Connie
--- Crystal <strive4peace> wrote:
>
> you're welcome, Connie ;)
>
>
> since you brought it up, I have a page explaining basic error handling here:
>
> http://www.AccessMVP.com/strive4peace/Code
>
>
> Warm Regards,
> Crystal
>
> *
> (: have an awesome day :)
> *
>
>
>
> ________________________________
> From: mrsgoudge
>
> Crystal, Graham and John,
>
> Thanks for you answer! I really appreciate all of you! In the future I will put it in the Error Procedure using your examples.
>
> Connie
>
> --- "John Viescas" wrote:
> >
> > Connie-
> >
> > You can set = Nothing (which will also close them if open), but if you try to
> > .Close a recordset that is not open, you will get an error.
> >
> > John Viescas, author
> > Microsoft Office Access 2010 Inside Out
> > Microsoft Office Access 2007 Inside Out
> > Building Microsoft Access Applications
> > Microsoft Office Access 2003 Inside Out
> > SQL Queries for Mere Mortals
> > http://www.viescas.com/
> > (Paris, France)
> >
> >
> >
> > -----Original Message-----
> > From: mrsgoudge
> >
> > In an event several recordsets are created. Some of them are not used in
> > certain instances where the sub exits because of conditions. In the Exit
> > Procedure Can I close and set = Nothing all the recordsets that were created at
> > the beginning even though they were not set to anything?
> >
> > Thanks!
> > Connie
> >
> >
[Non-text portions of this message have been removed]
Tidak ada komentar:
Posting Komentar