blue screen

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I crashed (blue screen) a computer by connecting Excel to an Access db
sitting on it. I used ADO, and the problem happened when I tried a datediff
that overflowed.

Is this a known bug?
 
Even though using ADO in Access does no harm, using ADO within Excel is a
known memory leak, which I have attempted to use ADO just pulling data from
one worksheet to another only to have the program eventually crash due to
this memory leak issue. I never seen the whole system itself crash though
due to this sort of issue using ADO within Excel VBA. For this reason, I
avoid using ADO within Excel like the plague.

Since dates in Excel are stored as double date types, if you aren't
potentially dealing with one date prior to January 1, 1900 and another date
after that date, then you can just take the difference between the 2 dates
to get how many days are apart from each other.

--

Sincerely,

Ronald R. Dodge, Jr.
Master MOUS 2000
 
Thanks! It's always nice to know that I'm not crazy (contrary to popular
belief). Do you know if this got fixed in Excel 2007?
 
I do not know if this has been fixed in 2007, though would not surprise me
one bit if it has not been fixed. Also, don't attempt to use MS Query as it
also uses ADO not to mention I have found it to be very cumbersome to use as
compared to other stuff that I have used.

Yeah, I get the response by a lot of people something to the effect that I
blow them out of the water or why am I working for the current company cause
of what I have happening within Excel, though definitely not limited to,
including the production reporting system that I personally built within
Excel (Client side for operators to use via Userforms in VBA, Server side to
update our main DB system, and what I generally refer to as my reporting
system for gathering the data and putting into reports that end users use
for their information).

--

Sincerely,

Ronald R. Dodge, Jr.
Master MOUS 2000
 
Back
Top