[AccessD] Debugging

XP won't always let you step into code either.  Once it gets the bit in
its teeth, it refuses to stop.  What happens if you put a breakpoint in
the code?  In XP, anyhow, it at least comes back and says it can't break
into code right now.

Charlotte Foust

-----Original Message-----
From: Martin Reid [mailto:mwp.reid at qub.ac.uk] 
Sent: Tuesday, August 05, 2003 12:55 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Debugging


Sorry it will not step into the code at all.

Martin


----- Original Message ----- 
From: "Charlotte Foust" <cfoust at infostatsystems.com>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Tuesday, August 05, 2003 1:47 PM
Subject: RE: [AccessD] Debugging


> What does "doesn't work" mean in this context, Martin?  It won't let 
> you break into code, or what?  Does it give you an error message?
>
> Charlotte Foust
>
> -----Original Message-----
> From: Martin Reid [mailto:mwp.reid at qub.ac.uk]
> Sent: Tuesday, August 05, 2003 12:43 PM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] Debugging
>
>
> Sitting in the VBA IDE in Access 2003 (Should not matter). Whatever I 
> try to step into some code it dosnt work. Any ideas?
>
> Martin
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com 
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com 
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com 
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com