Date problem with Access 97

[Steve]

Hi

I have a site using an access 97 application deployed with the runtime
version of access 97 i.e no development environment
on their PC's.

A few days ago their hardware people were on site and "something" was
changed on the PC. The result of the change
is as follows :

Any report that has a text box with the control source set to

=Date()

On the property sheet, no longer displays the date instead #NAME$ is
displayed.

The application has been running for over 2 years (without any problem) and
I can not simulate the problem on another PC.

Can anyone please assist

TIA
Steve

[Allen Browne]

There is a fairly good chance that something has messed up the references on
the errant PC.

Reinstalling your runtime may fix the problem. Using RegEdit to re-register
each library should also work.

If you are not familar with using RegEdit to fix references, see:
http://allenbrowne.com/ser-38.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Steve" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:c8**********@ctb-nnrp2.saix.net...

I have a site using an access 97 application deployed with the runtime
version of access 97 i.e no development environment
on their PC's.

A few days ago their hardware people were on site and "something" was
changed on the PC. The result of the change
is as follows :

Any report that has a text box with the control source set to

=Date()

On the property sheet, no longer displays the date instead #NAME$ is
displayed.

The application has been running for over 2 years (without any problem) and I can not simulate the problem on another PC.

[Steve]

Thanks for the response, I have uninstalled and reinstalled the application,
but with no luck

Steve

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:40***********************@freenews.iinet.net. au...

There is a fairly good chance that something has messed up the references on the errant PC.

Reinstalling your runtime may fix the problem. Using RegEdit to re-register each library should also work.

If you are not familar with using RegEdit to fix references, see:
http://allenbrowne.com/ser-38.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Steve" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:c8**********@ctb-nnrp2.saix.net...

I have a site using an access 97 application deployed with the runtime
version of access 97 i.e no development environment
on their PC's.

A few days ago their hardware people were on site and "something" was
changed on the PC. The result of the change
is as follows :

Any report that has a text box with the control source set to

=Date()

On the property sheet, no longer displays the date instead #NAME$ is
displayed.

The application has been running for over 2 years (without any problem)

and

I can not simulate the problem on another PC.

[Allen Browne]

Which references are you using (Tools | References from code window)?

Can you get your client to locate the files (dll/ocx/whatever) and
reregister them each with RegEdit on the problem machine?

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Steve" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:c8**********@ctb-nnrp2.saix.net...

Thanks for the response, I have uninstalled and reinstalled the application, but with no luck

Steve

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:40***********************@freenews.iinet.net. au...

There is a fairly good chance that something has messed up the

references on

the errant PC.

Reinstalling your runtime may fix the problem. Using RegEdit to

re-register

each library should also work.

If you are not familar with using RegEdit to fix references, see:
http://allenbrowne.com/ser-38.html

[Steve]

That is my next step.

Steve
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:40***********************@freenews.iinet.net. au...

Which references are you using (Tools | References from code window)?

Can you get your client to locate the files (dll/ocx/whatever) and
reregister them each with RegEdit on the problem machine?

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Steve" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:c8**********@ctb-nnrp2.saix.net...

Thanks for the response, I have uninstalled and reinstalled the

application,

but with no luck

Steve

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:40***********************@freenews.iinet.net. au...

There is a fairly good chance that something has messed up the

references

on

the errant PC.

Reinstalling your runtime may fix the problem. Using RegEdit to

re-register

each library should also work.

If you are not familar with using RegEdit to fix references, see:
http://allenbrowne.com/ser-38.html