Access Database

U

Uncle Sam

I have a database on a server for our entire team to make entries. We have a
problem that has arisen in the past couple of weeks on the input form. Only
several people on the team encounter the problem. When these people open the
input form, the date block (which should automatically contain the current
date) contains "Name#" in lieu of the date. Once the individual overwrites
the error with the date and moves to another record, the input form functions
correctly. I am at a loss as to why this happens and why it only happens to
several people and not everyone.
 
J

Jeff Boyce

Take a look at one of the affected PCs. Open the Access application in
database view, go to the modules, and open a module. Click on Tools |
References. Is one of the checked references marked "MISSING"?

If so, note which one, uncheck it and close/OK the window. Now, open it
again and re-check the reference, close/OK it.

Click Debug, Compile. The application should compile successfully.

Alternatively, make a copy of the front-end from a PC on which the
application IS working, and copy it over the front-end on the flakey PC.
You ARE using front-end/back-end design, right?!

--
Regards

Jeff Boyce
Microsoft Office/Access MVP


Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

Microsoft Registered Partner
https://partner.microsoft.com/
 
U

Uncle Sam

Jeff,

I know enough to be dangerous. I'm not sure what you mean by front
end/back end. I have the tables split from the database but both the tables
and the database are located on the server. Anyhow, I followed your
instructions on 1 of those with the problem. The reference was marked
missing and is now gone and the input form functions correctly. I'll do it
on the remaining computers now.

Thank You!

Doug
 
D

Douglas J. Steele

You really should distribute a copy of the front-end to each user so that
they have it on their hard drive.

Sharing the front-end significantly increases the probability of corruption.
As well, since the reference problem is caused by problems with the required
files on each user's hard drive, fixing it for User A may well break it for
Users B & C.
 
A

Aaron Kempf

front end back end?

don't listen to this CRAP

use SQL Server and Access Data Projets

MDB doesn't run over _ANY_ network reliably
don't blame it on the VPN-- ADP works great over a VPN
don't blame it on the WAN-- ADP works great over a WAN

BLAME IT ON MDB

MDB IS CRAP
USE ADP
 
A

Aaron Kempf

if you have a 'database on a server' then use Access Data Projects

MDB isn't reliable enough for real world usage
 
Top