Thanks. That was our first response. The same front end works properly on
other workstations. When recopied to this workstation it does not. It seems
as if windows/access may have prompted an inattentive user about making a
change. Without looking up or being aware of what was on the screen they
triggered the change and then observed the notice that "windows will need to
reboot". The change in behavior of the database followed the reboot.
> The front-end on that workstation is probably corrupt. The easiest fix is to
> copy a front-end from a working machine.
[quoted text clipped - 20 lines]
> > happened and how to restore it. If anyone has an idea please give me a
> > suggestion. Thanks.
The is nothing within Access that would ask Windows to reboot. The only
possible request might come from a Service Pack. Check the levels on
different machines by going to Help >>> About
Or possibly a computer virus. Check with the Windows or security newsgroups
for possible candidates. If you have a serious virus, and don't have a
really skilled person to deal with it, you might consider formatting the
hard drive and re-installing. It's a drastic step, but sometimes necessary.
The best bet though is to find a local MCSE to deal with the problem, if you
can't get an answer on-line

Signature
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
> Thanks. That was our first response. The same front end works properly on
> other workstations. When recopied to this workstation it does not. It
[quoted text clipped - 34 lines]
>> > happened and how to restore it. If anyone has an idea please give me a
>> > suggestion. Thanks.
OldEnough - 02 Mar 2008 04:10 GMT
I found the solution earlier today from another posting. Apparently the user
at this particular workstation did not notice that Microsoft Office Automatic
Updates initated an update to 2003 SP3. There is a known issue with this
update relating to combobox display. I found a link to the knowledgebase
article in another posting. The current workaround involves removing the
default formating of text fields in the front end. I implemented this
workaround and it restored the functionality of the backend on the affected
workstation. Presumably there should not be any adverse affect to the
database from this workaround.
> The is nothing within Access that would ask Windows to reboot. The only
> possible request might come from a Service Pack. Check the levels on
[quoted text clipped - 44 lines]
> >> > happened and how to restore it. If anyone has an idea please give me a
> >> > suggestion. Thanks.