B
billmiami2
(Note that this message was posted a few days ago in
comp.databases.ms-access)
We are having trouble with an MS Access 2000 application. The
application is set up in the standard fashion with a database mdb and a
user interface mdb with links from the user to the data file. Some of
the problems experienced include:
*continuous form subforms go "gray" and seem to lose their connection
with data after being requeried. Errors are generated when trying to
access the data in the subform after requerying. A workaround of
resetting the subform recordsource instead of requerying it has been
implemented which seems to be working for now.
*a combobox unexplainably goes blank such that none of the entries has
any text even though the entries still seem to exist. I can't tell
what exactly triggers this as the combobox isn't being requeried.
These problems only occur on certain servers set up with Windows
advanced server (SP4) and MS Office 2002. There are no problems at all
when the application is run on the following:
Windows XP workstations with Office 2002
Windows 2000 Pro (SP4) workstation with Office 2000
Windows 2000 Server (SP4) with Office 2000
Has anyone seen anything like this? What could be the problem?
Bill E.
Hollywood, FL
comp.databases.ms-access)
We are having trouble with an MS Access 2000 application. The
application is set up in the standard fashion with a database mdb and a
user interface mdb with links from the user to the data file. Some of
the problems experienced include:
*continuous form subforms go "gray" and seem to lose their connection
with data after being requeried. Errors are generated when trying to
access the data in the subform after requerying. A workaround of
resetting the subform recordsource instead of requerying it has been
implemented which seems to be working for now.
*a combobox unexplainably goes blank such that none of the entries has
any text even though the entries still seem to exist. I can't tell
what exactly triggers this as the combobox isn't being requeried.
These problems only occur on certain servers set up with Windows
advanced server (SP4) and MS Office 2002. There are no problems at all
when the application is run on the following:
Windows XP workstations with Office 2002
Windows 2000 Pro (SP4) workstation with Office 2000
Windows 2000 Server (SP4) with Office 2000
Has anyone seen anything like this? What could be the problem?
Bill E.
Hollywood, FL