Weird "Division by zero error"..

  • Thread starter Thread starter Frenchie
  • Start date Start date
F

Frenchie

Hello !

I have an Access 2002 application running fine on many PC's.

But some other, I get the following error upon a form's load :

Runtime error 11 : Division by 0

Clicking on "Debug" highlight the following line :

Debug.Print "Form frm1 Load " & Timer

Any idea ?

Thanks
 
Frenchie said:
Hello !

I have an Access 2002 application running fine on many PC's.

But some other, I get the following error upon a form's load :

Runtime error 11 : Division by 0

Clicking on "Debug" highlight the following line :

Debug.Print "Form frm1 Load " & Timer

Any idea ?

Thanks
Click to expand...

Did you get any answers on this?
 
Le 2006-08-29, Smartin a supposé :
Did you get any answers on this?
Click to expand...

Not at all.. Neither from the group nor from my own analysis
comparing the setup of two machines reacting differently.

Why ? Are you experiencing something similar ?
 
Access MDB is unmanageable.

Use Access Data Projects; when worst comes to worse; you can always use
profiler to watch for problems.

TRY DOING _THAT_ in silly MDB

-Aaron
ADP Nationalist
 
Frenchie said:
Le 2006-08-29, Smartin a supposé :

Not at all.. Neither from the group nor from my own analysis comparing
the setup of two machines reacting differently.

Why ? Are you experiencing something similar ?
Click to expand...

Sorry no, just curious. Seems the Timer object is throwing something
untoward? Thinking out loud, does even Timer exist on the form's load
event?
 
Dans son message précédent, Smartin a écrit :
Sorry no, just curious. Seems the Timer object is throwing something
untoward? Thinking out loud, does even Timer exist on the form's load event?
Click to expand...

Yes - Timer here is not the Timer object, it's a VBA statement giving
the number of seconds elapsed since last midnight. There's another one
at the end of the form load procedure. I use this in my applications
development to measure the time requied for a form to load.

What's weird here is that there's nothing in this statement that can
cause a "division by zero".
 
Frenchie said:
Dans son message précédent, Smartin a écrit :

Yes - Timer here is not the Timer object, it's a VBA statement giving
the number of seconds elapsed since last midnight. There's another one
at the end of the form load procedure. I use this in my applications
development to measure the time requied for a form to load.

What's weird here is that there's nothing in this statement that can
cause a "division by zero".
Click to expand...

Well I'm baffled. Doesn't help that I can't reproduce it. ? Suggest you
wrap some error handling around this malfeasant function. Curious to
know if, after trapping an error at the beginning of on_load if you get
the same error at the end of the procedure?
 
my reccomendation is 'dont use MDB' it is too buggy for real-world use.

you can keep many of your existing architectures; including forms and
reports-- if you would just get off your fat lazy ass and learn Access
Data Projects.

ADP doesn't just 'randomly throw errors' like MDB does.

-Aaron
ADP Nationalist
 
Back
Top