Re: mysterious lockup of form half-way through ADO code
- From: "Sirocco" <NB2002@xxxxxxxxxx>
- Date: Fri, 27 May 2005 14:13:40 -0400
Thank you, it works.
"Graham R Seach" <gseach@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:#YnpYMlYFHA.3152@xxxxxxxxxxxxxxxxxxxxxxx
> Whether you're using ADO or DAO is irrelevent, because the code in
question
> is VBA.
>
> You should really be using:
> !BeginTime = DateAdd("s", 4, Now())
>
> Regards,
> Graham R Seach
> Microsoft Access MVP
> Sydney, Australia
>
> Microsoft Access 2003 VBA Programmer's Reference
> http://www.wiley.com/WileyCDA/WileyTitle/productCd-0764559036.html
>
>
> "Sirocco" <NB2002@xxxxxxxxxx> wrote in message
> news:e39Uy5kYFHA.2860@xxxxxxxxxxxxxxxxxxxxxxx
> > The following expression works on my PC running Windows NT.
> >
> > !BeginTime = Now() + #12:00:04 AM#
> >
> > It puts the current time plus 4 seconds in the field called BeginTime.
> > (generally, the VB is the ADO version)
> >
> > On a different PC, running Windows XP, it also works (I know because the
> > field has the current time plus 4 seconds added to it) but then Access
> > completely locks up, the rest of the procedure doesn't execute, with no
> > error message, and I have to ctrl-alt-del to get out.
> >
> > What the heck is going on?
> >
> > I'd appreciate any response.
> >
> > Thanks.
> >
> >
>
>
.
- References:
- mysterious lockup of form half-way through ADO code
- From: Sirocco
- Re: mysterious lockup of form half-way through ADO code
- From: Graham R Seach
- mysterious lockup of form half-way through ADO code
- Prev by Date: Re: Sum of a field
- Next by Date: Re: Code to see if a value exists in table
- Previous by thread: Re: mysterious lockup of form half-way through ADO code
- Next by thread: User input found in data
- Index(es):
Relevant Pages
|
|
