2007 Runtime Problem?

  • Thread starter Thread starter kt2902
  • Start date Start date
K

kt2902

I have a subform which calculates the number of days from the range of dates
entered by the user. It then places this number on the main form. Works
great, does everything I need it to - no problems......

Some of my clients reported that no matter what they did, the total on the
main form stayed at zero. On further investigation, it appears that the only
difference with these particular clients is they are running 2007 runtime.

Could this be causing the problem and what do I do about it?
 
DateDiff() should work the same in the runtime.

Any chance there's a problem with library references?

Perhaps the runtime needs to be undated with a service pack?

Any chance Access may not be understanding the values as dates? (E.g. if the
text boxes are unbound, set their Format property to General Date so it
interprets the data type correctly.)

Could user permissions be an issue?
 
On Mon, 8 Jun 2009 20:16:01 -0700, kt2902

Use the /runtime command line switch to debug this further. Also ask
yourself if ALL runtime installations have this problem, or just some.

-Tom.
Microsoft Access MVP
 
Wow, that's a whole lot of stuff to work through! I'll start at the top and
work my way down and let you know how I got on.

Thanks again Allen
 
When I use the /runtime switch I don't get the problem, I think because I am
not using 2007. Only the users who have 2007 runtime are having this problem.
Everyone else is fine.
 
kt2902 said:
I have a subform which calculates the number of days from the range of
dates
entered by the user. It then places this number on the main form. Works
great, does everything I need it to - no problems......

Some of my clients reported that no matter what they did, the total on the
main form stayed at zero. On further investigation, it appears that the
only
difference with these particular clients is they are running 2007 runtime.

Could this be causing the problem and what do I do about it?
Click to expand...


Is the calculation performed by VBA code? Is it possible that the Access
2007 users don't have the database stored in a trusted location, so all VBA
code is disabled? Can you verify that other VBA code in the database is
running?
 
Hi Dirk, yes all other code works fine, except for this one calculation which
isn't done in VBA, just on the form itself. The user enters the start date
and the end date and the number of days is calculated. Then there is a grand
total at the bottom of the subform and it is this figure which should then be
displayed on the main form.
 
kt2902 said:
Hi Dirk, yes all other code works fine, except for this one calculation
which
isn't done in VBA, just on the form itself. The user enters the start date
and the end date and the number of days is calculated. Then there is a
grand
total at the bottom of the subform and it is this figure which should then
be
displayed on the main form.
Click to expand...


Hmm. That *could* be the operation of Jet Sandbox Mode, though I'm not
sure. Look up sandbox mode in the online help, and/or see this link:

http://office.microsoft.com/en-us/access/HA012301901033.aspx
 
I had a look at the link and the only thing I could see that was relevant to
what I am I doing was the Parent reference. So I removed that from my code
and tried again, but the problem is still occurring. The other thing I have
noticed during all this testing is that not only is the total on the Main
Form not updating, but if it already contains a number it is being reset to 0
when I add new data to the subform. So now I'm even more confused.
 
kt2902 said:
I had a look at the link and the only thing I could see that was relevant
to
what I am I doing was the Parent reference. So I removed that from my code
and tried again, but the problem is still occurring. The other thing I
have
noticed during all this testing is that not only is the total on the Main
Form not updating, but if it already contains a number it is being reset
to 0
when I add new data to the subform. So now I'm even more confused.
Click to expand...


It could be something else operating, of course, but I seem to recall
running into a similar situation, where it turned out that sandbox mode was
not permitting user-defined VBA functions to be called directly from event
properties.
 
Back
Top