disk network error

[Lucky]

Since converting to Access 2003, the users are getting a
disk or network error which forces them to close down the
database and get back on again. There was NEVER this
error when they were on Access 97. When I approach the
network people they say that it can't be them since 97
was fine. Are there any settings that I could do? I have
tried deleting the links and re-adding them. It was also
suggested somewhere that the caching be turned off which
made it worse and corrupted the database so bad that it
had to be restored from tape. Please help!! The users are
starting to get mean.

Lucky (or not so Lucky right now)

 

[John Nurick]

What actual error numbers and error messages are they getting? Does this
happen wit one database or every database? Is it every user or just some
users?

Is the database split, with a copy of the front end on each workstation?

 

[Lucky]

There is no error number, it just says disk or network
error and then they are not connected anymore...they
can't save their records. It is with one dept in one of
our plants and this is the only database that they run.
However, my boss has tried to reproduce the problem from
our location and has not been able to make it happen.
Any help would be greatly appreciated.
Lucky

-----Original Message-----
What actual error numbers and error messages are they getting? Does this
happen wit one database or every database? Is it every user or just some
users?

Is the database split, with a copy of the front end on each workstation?

Since converting to Access 2003, the users are getting a
disk or network error which forces them to close down the
database and get back on again. There was NEVER this
error when they were on Access 97. When I approach the
network people they say that it can't be them since 97
was fine. Are there any settings that I could do? I have
tried deleting the links and re-adding them. It was also
suggested somewhere that the caching be turned off which
made it worse and corrupted the database so bad that it
had to be restored from tape. Please help!! The users are
starting to get mean.

Lucky (or not so Lucky right now)

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.

 

[John Nurick]

I've searched a little but haven't found anything obviously relevant.

You haven't said whether the database is split or whether the front end
is shared. It should be split, with a copy of the front end on each
workstation.

Does the problem occur on all the workstations in the department, or
just on one or on some of them? Was anything else changed at the time
Office 2003 was installed (e.g. new hardware, operating system
upgrades)?

There is no error number, it just says disk or network
error and then they are not connected anymore...they
can't save their records. It is with one dept in one of
our plants and this is the only database that they run.
However, my boss has tried to reproduce the problem from
our location and has not been able to make it happen.
Any help would be greatly appreciated.
Lucky

-----Original Message-----
What actual error numbers and error messages are they getting? Does this
happen wit one database or every database? Is it every user or just some
users?

Is the database split, with a copy of the front end on each workstation?

Since converting to Access 2003, the users are getting a
disk or network error which forces them to close down the
database and get back on again. There was NEVER this
error when they were on Access 97. When I approach the
network people they say that it can't be them since 97
was fine. Are there any settings that I could do? I have
tried deleting the links and re-adding them. It was also
suggested somewhere that the caching be turned off which
made it worse and corrupted the database so bad that it
had to be restored from tape. Please help!! The users are
starting to get mean.

Lucky (or not so Lucky right now)

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.

 

[Lucky]

Thanks for sticking with me on this. It is a split
database. They are fighting having the front end on their
machine. I think it is because there are 3 shifts using
the same pc and they are afraid to have it on a c drive
where people can get to it. So they are all running it
from the same front end mdb. I will fight harder for the
front end to go on their machine - at least for a trial
run to prove if that works or not. Any other ideas would
be greatly appreciated. From what I have been led to
understand, they have all gotten new machines with the
upgrade.
Thanks, Lucky
P.S. Have a great Easter!

-----Original Message-----
I've searched a little but haven't found anything obviously relevant.

You haven't said whether the database is split or whether the front end
is shared. It should be split, with a copy of the front end on each
workstation.

Does the problem occur on all the workstations in the department, or
just on one or on some of them? Was anything else changed at the time
Office 2003 was installed (e.g. new hardware, operating system

upgrades)?




There is no error number, it just says disk or network
error and then they are not connected anymore...they
can't save their records. It is with one dept in one of
our plants and this is the only database that they run.
However, my boss has tried to reproduce the problem from
our location and has not been able to make it happen.
Any help would be greatly appreciated.
Lucky

-----Original Message-----
What actual error numbers and error messages are they getting? Does this
happen wit one database or every database? Is it every user or just some
users?

Is the database split, with a copy of the front end on each workstation?

On Thu, 8 Apr 2004 21:01:16 -0700, "Lucky"

Since converting to Access 2003, the users are

getting
a

disk or network error which forces them to close down the
database and get back on again. There was NEVER this
error when they were on Access 97. When I approach the
network people they say that it can't be them since 97
was fine. Are there any settings that I could do? I have
tried deleting the links and re-adding them. It was also
suggested somewhere that the caching be turned off which
made it worse and corrupted the database so bad that it
had to be restored from tape. Please help!! The users are
starting to get mean.

Lucky (or not so Lucky right now)

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.

 

[Ronald W. Roberts]

Thanks for sticking with me on this. It is a split
database. They are fighting having the front end on their
machine. I think it is because there are 3 shifts using
the same pc and they are afraid to have it on a c drive
where people can get to it. So they are all running it
from the same front end mdb. I will fight harder for the
front end to go on their machine - at least for a trial
run to prove if that works or not. Any other ideas would
be greatly appreciated. From what I have been led to
understand, they have all gotten new machines with the
upgrade.
Thanks, Lucky
P.S. Have a great Easter!

Cut

When you put the front end on the pc, make it an MDE not just a MDB.
This may help with their concerns.

Ron

 

[John Nurick]

It is a split
database. They are fighting having the front end on their
machine. I think it is because there are 3 shifts using
the same pc and they are afraid to have it on a c drive
where people can get to it.

Network and/or Access user-level security will take care of that!