duplicate data base error

[Guest]

I have created a database for conducting intra departmental user
satisifaction surveys. I have asked all of supv. in my departmtent to include
hyper links to the survey when solisiting responses. i have descovered that
one of two of supv's are not as computer savy as i thought and had sent the
survey out as a short cut.
here is my problem when the respondant completes the survey they get an
error message stating that there was a problem with the database and that
Access would create a duplicate. every day i have had to gointo the file and
delete the duplicates. for example the name of the data base is Survey, but i
have do get rid of DB1, DB2,DB3 etc. what should i do to avoid this
replication problem.

 

[BruceM]

Either send the link yourself, or prepare the message, including the link,
and make it available to supervisors for forwarding.

In general it is unwise (and unfair) to expect people to have skills outside
of those needed for their jobs.

Another possibility: I have assembled all shortcuts into a Shortcuts folder
that is available to all, usually on the desktop (although there are
different preferences on the subject). Such a folder may be an appropriate
place for such a shortcut; you could direct users to the folder.

A split database offers another way to avoid the sort of problem you
describe.

 

[Guest]

the data base is split the link has been to the front end only. so you feel
that the main problem has been the with the short cut link. our department
has an informational dashboard. i am planing on useing a direct link to the
survey from the dash board, and askin every one to asses the survey from
there.

 

[BruceM]

The usual procedure with a front end is to give a copy to each user. I know
from experience that links can be troublesome. A lot of people don't seem
to grasp the difference between a link and a copy ("All I know is that it
works"), but sooner or later it becomes a problem that the person is using a
different file than his or her co-workers.
This is not to say that links should not be used, but rather that they need
to be tended carefully. I suppose it's possible to share a front end, but I
can't think of a reason why you would want to.