Bug In Access 2002 Runtime When Installed On Win XP SP2

F

FlyGuy

We distribute an Access 2002 application using Access 2002 RT. The app is
coded with VBA. We use the Office XP Developer Packaging Wizard to creade a
setup.

We are now finding that if the install in made on a XP SP2 box (i.e., SP2
was there before our app is installed), the "=Date()" VBA function does not
render a result if used as the on-open default value for controls on forms
(while adding new record) or reports. The displayed value is "NAME?" instead
of the current date. However, the function seems to otherwise work properly
if used within a VBA procedure.

This does not seem happen if Access 2002 Runtime was on a box before the box
was upgraded from XP to XP SP2.

This is being reported to us by several unrelated users.

Note: we cannot reproduce this on our test boxes internally because they
were XP boxes with RT in place that were subsequently upgraded to SP2.
However, we have seen this behavior on other's boxes.

We suspect some issue between SP2 system files and Office system files. It
may also involve how the Office Update web site works post SP2?

The app installs and works OK on Win98SE, Win2000, and WS2003. We just seem
to get the problem on XP SP2 boxes.

A user can manually type in a date over the "Name?" and all is OK. But we
need the value to be inserted automacially.

Can anyone assist?

We have a free downloadable demo at http://www.cookbookplus.com if anyone
wants to try and reproduce. 130 MB; highspeed internet required.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top