Re: EDatabase Error with ADO Query

From: Brian Bushay TeamB (BBushay_at_Nmpls.com)
Date: 10/27/04 

Date: Tue, 26 Oct 2004 19:08:15 -0500

>Brian thank for the advice and I know I can do that. There are about 50
>variables in this table that I need at various points in the program. I
>wanted to avoid have to check if the table is active each time I make a call
>to a field in the table.... won't that slow down the process?

Checking if the table is active won't take any appreciable time. Opening it if
it is closed will take some time so it would be best to find out where it is
being closed.
You could write an Onclose event for the dataset and put a debug point in it.
Then when you get to the debug look at the call stack or try single stepping
through the code to find the line where it is being closed. 

--
Brian Bushay (TeamB)
Bbushay@NMPLS.com

Relevant Pages

  • Re: Need Help Debugging
    ... you should use straight and plain ADPlus.VBS from the debugger package. ... debug info loaded, etc... ... InitializeCriticalSection in order to avoid memory resource exceptions ... does that avoid using the stack ?!? ...
    (microsoft.public.win32.programmer.kernel)
  • about call stack
    ... When I debug my program, it's easily to meet a "call stack is unavailable" ... How could I avoid this?Someone points me? ... Prev by Date: ...
    (microsoft.public.vstudio.general)
  • Call Stack
    ... When I debug my program, it's easily to meet a "call stack is unavailable" ... How could I avoid this?Someone points me? ... Prev by Date: ...
    (microsoft.public.vc.debugger)
  • Re: Bug in .NETs Process model?
    ... Debug.WriteLine does not output anything in Release mode - only in debug ... If this is a general method, I would read both std out and std err in ... seperate threads so you don't block forever if you have some program waiting ... > so I was tryng to avoid it... ...
    (microsoft.public.dotnet.framework)
  • Re: any macro-like construct/technique/trick?
    ... > * the two-lines of debug conditional tend to really break up the flow ... I want to avoid such unnecessary waste ... though I would use the do-nothing function version I sketched ...
    (comp.lang.python)