Disk or Network Error.

[Lewe22]

I have created a secured access database which contains the following....
On Server: Back End
On Client PC: Front End, Workgroup and Shortcut (to point user through workgroup)

The workgroup i have created contains two log ins: SuperUser - (With privileges to create and edit all objects) and CallManagement - (With restricted user access).

When logged on as the SuperUser from my machine i have full access to the entire database, but when logged in as SuperUser from another PC as soon as i try to view or use data in a table i am seeing 'Disk or Network Error'.

Does anyone have any ideas? I'm lost??

[NeoPa]

We don't have access to the whole situation here (always hard - it's a web page after all), but I would guess this is not anything to do with the workgroup file per se (from what you say).

Are you getting similar errors when attempting to access the db as CallManagement from the other PCs?

[Lewe22]

Hi Neo, yes. It's very strange. I'm at a loss as to why this is happening. All other machines i have tried this on are experiencing the same problems. It's not about access to the back end on the server as everyone has full permissions to the folder...

[NeoPa]

Yes? So you are you getting similar errors when attempting to access the db as CallManagement from the other PCs.

I would expect that to indicate that the workgroup file (internally at least) is not the issue. Possibly correctly accessing it may be.

What leads you to think that may be the cause?

[Lewe22]

Yes. It happens when logged on as SuperUser or CallManagement. I'm just not really aware of what else it may be as i have ruled out the network access.

It may be worth noting that this error is occurring when trying to access any table info from a form (eg: when selecting the drop down for a combo box which looks up from a table) and not when initially logging in.

[hjozinovic]

Hi L.
To me it seems there might be 3 possible problems:

1. Do you have workgroup file on all client PCs?
Not sure if i'm doing it correct but I have similar situation and my workgroup file is associated with BackEnd database. This way only one workgroup file is used and it's working great for me. Maybe you could do that instead of making shortcuts, and copying workgroup file to each and every user PC.

2. If FrontEnd is developed on your PC and distributed to other users you should make sure the tables are linked correctly to the database because the path to the database is now changed for them.
Make sure they run Linked Table Manager and refresh the link to the database.

3. Reffering to folder that contains BackEnd database.
Make sure administrator of the folder gives the right permissions for the users.
These permissions are controled on the BackEnd database itself and as well on the folder level.
Right click on the database/folder->Properties->Security...

H.

[NeoPa]

I'm not entirely convinced that it's not Network related. There are so many possible issues that eliminating them all is very hard to achieve.

There is the nub of the problem for me helping I'm afraid : as you don't know where the problem lies you can't give me the information that might point me in the right direction. Simply that it behaves differently on different PCs could point to so many different things, I have no way of helping I'm afraid.

It won't hurt to try out some of H's suggestions and see where that gets you. I'll continue to monitor the thread in case any further info sheds any light for me, but I can't promise anything.

[Lewe22]

Thanks for everyone's help. Really appreciate how quickly you all came back to me!

I have resolved my problem using hjozinovic's suggestion (below)

If FrontEnd is developed on your PC and distributed to other users you should make sure the tables are linked correctly to the database because the path to the database is now changed for them.
Make sure they run Linked Table Manager and refresh the link to the database.

In my particular case all tables in the front end were in fact pointing to my development database which was located on my d: drive and not the server.
A rookie mistake!

To correct this (as kindly suggested!) i refreshed all the tables and pointed
them to the server address eg: \\ukuksles16\uk and ireland sales\Call Management\Data base BE

Thanks again everyone, hopefully i'll be able to help you out in the future!!

[NeoPa]

Excellent :)

Another member helped H. You're getting to be a real asset :)

[hjozinovic]

Glad to be of help. I got help here and in return I'm trying to give something back. Hope others would do the same. It gives you opportunity to learn something new every day and stay sharp.

And something importaint, Lewe thanks for letting us know you solved it. We allways need to know did it finally worked or not. Some people just leave and then we are wondering did it helped or not.
regards, H.