By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,822 Members | 1,042 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,822 IT Pros & Developers. It's quick & easy.

networking the db

jayme
P: 83
Ok-I have a question about putting our database out on the network. The guy that was helping me with this went out of town and it seemed to be working when he was here but now we are having some issues so any help would be SO MUCH APPRECIATED! :-)

Well I created this db for a multiple users. I made it to where you have to have a login name and password to get into the db. When I was finished I saved it out on our network, but when other people went to open the db it was not asking them for a password to get in-although it was working when I opened it on my computer....
So what we did was we made a .BAT file that included the following:
ECHO OFF
START "C:\Program Files\Microsoft Office\Office\Msaccess.Exe" "T:\Trades\Database\vioxJOBtrack.mdb" /wrkgrp "T:\Trades\Database\TRADESGRP.mdw"
Then we made that file into an .exe application file. On my computer this does work - so I open the .exe file and it opens a dos window, locates the file it needs to be opening, then the database opens and the dos window closes. And the db is there, open, its good to go.
BUT when someone else was testing it - he went to the network drive, clicks on the .exe file, the dos window opens but the db never opens. Then the dos window closes. So pretty much, it doesnt work on his computer.

I tried explaining this the best I could-I'm sure I missed some details, possibly...so just let me know if you have any questions!!
Any ideas on what the problem could be.
THANKS!!
Jun 5 '07 #1
Share this Question
Share on Google+
22 Replies

puppydogbuddy
Expert 100+
P: 1,923
Ok-I have a question about putting our database out on the network. The guy that was helping me with this went out of town and it seemed to be working when he was here but now we are having some issues so any help would be SO MUCH APPRECIATED! :-)

Well I created this db for a multiple users. I made it to where you have to have a login name and password to get into the db. When I was finished I saved it out on our network, but when other people went to open the db it was not asking them for a password to get in-although it was working when I opened it on my computer....
So what we did was we made a .BAT file that included the following:
ECHO OFF
START "C:\Program Files\Microsoft Office\Office\Msaccess.Exe" "T:\Trades\Database\vioxJOBtrack.mdb" /wrkgrp "T:\Trades\Database\TRADESGRP.mdw"
Then we made that file into an .exe application file. On my computer this does work - so I open the .exe file and it opens a dos window, locates the file it needs to be opening, then the database opens and the dos window closes. And the db is there, open, its good to go.
BUT when someone else was testing it - he went to the network drive, clicks on the .exe file, the dos window opens but the db never opens. Then the dos window closes. So pretty much, it doesnt work on his computer.

I tried explaining this the best I could-I'm sure I missed some details, possibly...so just let me know if you have any questions!!
Any ideas on what the problem could be.
THANKS!!
Sounds to me like you forgot to map the network drive on the other computer. Go to Windows Explorer and select Tools>Map Network Drive on each computer that is to be in that shared directory.
Jun 5 '07 #2

jayme
P: 83
Sounds to me like you forgot to map the network drive on the other computer. Go to Windows Explorer and select Tools>Map Network Drive on each computer that is to be in that shared directory.
Well I checked how my drive is mapped and then checked the other computer to see how that drive is mapped and both are the same. The db is out on a shared network( in our case it is on the T:\\ drive) So I checked how my T:\\ drive is mapped and how thier's is mapped and both are the same.

Any other options??

THANKS!
Jun 5 '07 #3

puppydogbuddy
Expert 100+
P: 1,923
Well I checked how my drive is mapped and then checked the other computer to see how that drive is mapped and both are the same. The db is out on a shared network( in our case it is on the T:\\ drive) So I checked how my T:\\ drive is mapped and how thier's is mapped and both are the same.

Any other options??

THANKS!
1. Verify that user that is accessing shared directory has full permissions (read, write) on that directory..
2. Are you booting the applicaton from a shortcut...make sure shorcut properties are correct....should show network path.
3. Boot MS Access up by itself/then try selecting the application from the file list...what happens?
Jun 5 '07 #4

jayme
P: 83
1. Verify that user that is accessing shared directory has full permissions (read, write) on that directory..
2. Are you booting the applicaton from a shortcut...make sure shorcut properties are correct....should show network path.
3. Boot MS Access up by itself/then try selecting the application from the file list...what happens?
1. I will have to check with the IT Dept here to see if they have granted him those permissions on that drive-the only thing is - I don't think I have those permissions...maybe I do-but we should have the same permissions as "Users". I'll have to look more into that.
2. Right now we are going straight to the location on the drive-not using a shortcut. We eventually would like to just put the shortcut on the desktop and use that-but we need to get it working first! :-)
3. The only problem with doing it this way is that the file we are opening is an .exe file not an actual access db file. We created this so this opens up a dos window-locates the db file on the network then opens the db..(not sure how to explain it with all the technical terms-but hopes that makes sense). That is what the guy that went on vacation was working on before he left-which I thought worked-well, it works for me at least. So all that to say-when they go to open up Access then locate the file it isn't there becuase it isn't an actual access file.
Jun 5 '07 #5

puppydogbuddy
Expert 100+
P: 1,923
1. I will have to check with the IT Dept here to see if they have granted him those permissions on that drive-the only thing is - I don't think I have those permissions...maybe I do-but we should have the same permissions as "Users". I'll have to look more into that.
2. Right now we are going straight to the location on the drive-not using a shortcut. We eventually would like to just put the shortcut on the desktop and use that-but we need to get it working first! :-)
3. The only problem with doing it this way is that the file we are opening is an .exe file not an actual access db file. We created this so this opens up a dos window-locates the db file on the network then opens the db..(not sure how to explain it with all the technical terms-but hopes that makes sense). That is what the guy that went on vacation was working on before he left-which I thought worked-well, it works for me at least. So all that to say-when they go to open up Access then locate the file it isn't there becuase it isn't an actual access file.
Jayme,
I was not refering to the .exe file. I was trying to get you to see if you could bypass the .exe, and boot up the application (mdb file) from the file list. Then tell me what happens.
Jun 5 '07 #6

jayme
P: 83
Jayme,
I was not refering to the .exe file. I was trying to get you to see if you could bypass the .exe, and boot up the application (mdb file) from the file list. Then tell me what happens.
oh i see..sorry about that.
well the reason we are not having them open up the mdb file straight up is becuase for some reason it does not ask them for the user name and password to login (and we need it to do that becuase certain users can only have certain capabilities within the database)
but last time we tried that it opened up fine.-just that login thing was an issue.
Jun 5 '07 #7

puppydogbuddy
Expert 100+
P: 1,923
oh i see..sorry about that.
well the reason we are not having them open up the mdb file straight up is becuase for some reason it does not ask them for the user name and password to login (and we need it to do that becuase certain users can only have certain capabilities within the database)
but last time we tried that it opened up fine.-just that login thing was an issue.
Hi Jayme,
the reason I was asking about bypassing the .exe file was to test and see if the other computer had read/write permissions to the directory.

When you checked to see if the drive was mapped on the other computer, how did you do it? The best way to tell if the drive mapping was "actually" set on that computer is to go to the "MyComputer" icon on the desktop and see if you can browse to the directory. If you can't see it, then the drive mapping has not been set for that computer. I believe the first time the drive is mapped, the computer has to be rebooted in order for the drive mapping to set.

Access, itself has to be configured to work in network mode when running that application. If you go to Tools>Options> Advanced tab, you will see the various loading and locking options.
Jun 5 '07 #8

jayme
P: 83
Hi Jayme,
the reason I was asking about bypassing the .exe file was to test and see if the other computer had read/write permissions to the directory.

When you checked to see if the drive was mapped on the other computer, how did you do it? The best way to tell if the drive mapping was "actually" set on that computer is to go to the "MyComputer" icon on the desktop and see if you can browse to the directory. If you can't see it, then the drive mapping has not been set for that computer. I believe the first time the drive is mapped, the computer has to be rebooted in order for the drive mapping to set.
oh-ok-yes that computer is mapped to that drive. this drive is used for many things- so the computer i was testing it out on is able to get to the drive i have the db saved on. he is able to open up the folder see the files and everything-its just that when he clicks on it, the db never opens...and he does have MS Access on his computer.

Access, itself has to be configured to work in network mode when running that application. If you go to Tools>Options> Advanced tab, you will see the various loading and locking options.
I checked this and "Default open mode" is set to shared...


This just doesnt make sense to me how it is saved out on the network for everyone and it works when I open it and not when someone else tries to??
Thanks for your help tho-I really do appreciate it!
Jun 5 '07 #9

puppydogbuddy
Expert 100+
P: 1,923
oh-ok-yes that computer is mapped to that drive. this drive is used for many things- so the computer i was testing it out on is able to get to the drive i have the db saved on. he is able to open up the folder see the files and everything-its just that when he clicks on it, the db never opens...and he does have MS Access on his computer.



I checked this and "Default open mode" is set to shared...


This just doesnt make sense to me how it is saved out on the network for everyone and it works when I open it and not when someone else tries to??
Thanks for your help tho-I really do appreciate it!
Something else to check. First, exit the application from your computer if you are in the application. Then using "MyComputer", browse to the directory where the mdb file is located and make sure that a file with the same name as the application.mdb, but with a file extension of .ldb is not present. If the file with a ldb (stands for locked db) extension is present when noone is on the application, the application has activated but not released a record lock...this happens when the application has to shut down before the lock is released. In order to utilize the application after that happens, the application.ldb file has to be erased.
Jun 5 '07 #10

jayme
P: 83
Something else to check. First, exit the application from your computer if you are in the application. Then using "MyComputer", browse to the directory where the mdb file is located and make sure that a file with the same name as the application.mdb, but with a file extension of .ldb is not present. If the file with a ldb (stands for locked db) extension is present when noone is on the application, the application has activated but not released a record lock...this happens when the application has to shut down before the lock is released. In order to utilize the application after that happens, the application.ldb file has to be erased.
Checked that too...no ldb file.

Well this morning I tested opening the db from the network on another computer...it actually opened. Which is one step closer...not sure what the difference is between the computer I was trying before and this one but at least it opened..BUT it did not ask for the password like it was supposed to! That was the whole reason we created the BAT file then turned that into the exe file. It worked last week when I tried it...so I don't know what else to look for here...I think this one is a little over my head!
Jun 6 '07 #11

Expert 100+
P: 344
Checked that too...no ldb file.

Well this morning I tested opening the db from the network on another computer...it actually opened. Which is one step closer...not sure what the difference is between the computer I was trying before and this one but at least it opened..BUT it did not ask for the password like it was supposed to! That was the whole reason we created the BAT file then turned that into the exe file. It worked last week when I tried it...so I don't know what else to look for here...I think this one is a little over my head!
I think you may have just created a security file, the mdw, and not actually secured the database. On your pc, the other guy may have changed your default login to, say, newuser, which requires a password. On the other PCs, they access the file as Admin, no password and get straight in. Fully securing the access database needs carefull planning
Jun 6 '07 #12

jayme
P: 83
I think you may have just created a security file, the mdw, and not actually secured the database. On your pc, the other guy may have changed your default login to, say, newuser, which requires a password. On the other PCs, they access the file as Admin, no password and get straight in. Fully securing the access database needs carefull planning
When I have the db open I track the file back to the location where it is stored on the network and there is a LockFile for both the actual db and the mdw file. So wouldn't that mean that the security file is in fact connected to the db since it creates that as the db is open? Just want to clarify that before I go on.

also-i was looking more into this and saw somewhere where it said that all users must have read, write, create, and delete permissions for the folder in which the db is stored. so i am getting with my IT dept here to make sure all the users do in fact have those permissions..could that be causing these problems you think?
Jun 6 '07 #13

MMcCarthy
Expert Mod 10K+
P: 14,534
I think you need to look at Lysanders point about the setting up of the mdw file. You may not have properly set the security permissions for all users. I think Lysander may be able to help you with this so I'll leave it with him.
Jun 6 '07 #14

jayme
P: 83
I think you need to look at Lysanders point about the setting up of the mdw file. You may not have properly set the security permissions for all users. I think Lysander may be able to help you with this so I'll leave it with him.
does anyone have an idea how i can check to make sure all that is set up properly? because i followed the directions on how to do it..so im pretty sure that is all right but is there a way to make sure it is all connected properly??
thanks!
Jun 13 '07 #15

MMcCarthy
Expert Mod 10K+
P: 14,534
does anyone have an idea how i can check to make sure all that is set up properly? because i followed the directions on how to do it..so im pretty sure that is all right but is there a way to make sure it is all connected properly??
thanks!
It's not my area of expertise. However, you can check out this website which has pretty comprehensive information.

Access Security
Jun 13 '07 #16

jayme
P: 83
ok-i know i have set up this securtiy correctly..i have followed the directions step for step...but it is still not working. like i said-i open it up on my computer and it asks for the password-works fine...but on other computers they go and find the db out on the network open it and it does not ask for the password!!
any ideas here or is everyone stumped like i am!?! :-)
thank you!!
Jun 14 '07 #17

Denburt
Expert 100+
P: 1,356
ok-i know i have set up this securtiy correctly..i have followed the directions step for step...but it is still not working. like i said-i open it up on my computer and it asks for the password-works fine...but on other computers they go and find the db out on the network open it and it does not ask for the password!!
any ideas here or is everyone stumped like i am!?! :-)
thank you!!
I know I am diving in here (I haven't read all the posts) however you need to tell the database where the MDW file is located otherwise it will use the default file in the default location. If you set up the security on your PC then it is using your MDW file with security and they are using the one on their PC with no security. It has been a while since I worked with the MDW file however it is usually system.mdw and you can jump in and rename it relocate it etc. I used to use the developers edition of office so I could compile everything into an exe file for install purposes another method is copying everything by hand or writing a script for this then I would package it with the frontend to be installed on each users PC. I would bury it somewhere like in the windows system directory and use some oddball name like "win" and may or may not even use an extension.

If you want the Frontend to stay on the network then I am sure you can do something similar but you will need to play with it a bit.
Jun 14 '07 #18

Denburt
Expert 100+
P: 1,356
O.K. I had to do some digging so you might understand things a little better.

http://support.microsoft.com/kb/305542

One thing I try to stay away from is joining the workgroup file in the shortcut since they can locate the mdw. I wish i could remember more but as I said I was using the developers edition and I think they made things easier to secure with using that.
Jun 14 '07 #19

puppydogbuddy
Expert 100+
P: 1,923
Jayme,

In order for the MDW file to activate the logon process for the workgroup on each of the other PC's, each user has to be assigned to a user workgroup via Access user level security. See the following link...it provides a step by step for implementing User Level Security beginning on page 12 of the article [or pdf page 6]. You should also note that there is a Access Security Wizard (see article page 13 [or pdf page 7]) that is available to assist you in this process. As always, before doing anything, it is recommended that you make a backup of the unsecured version of your database before attempting to implement User Level Security.

http://www.uky.edu/~dsianita/622/access_security.pdf
Jun 14 '07 #20

jayme
P: 83
In order for the MDW file to activate the logon process for the workgroup on each of the other PC's, each user has to be assigned to a user workgroup via Access user level security.
I have assigned users to a certain group (other than Users or Admin) and made special permissions for that group. We created a batch file that was supposed to call up the db location then the workgroup security file we had created but it for some reason is not working on other computers.

This morning I went to another computer and went to the Workgroup Administrator (WRKGADM in Program Files) and changed the system.mdw to the security file that I have created. This allowed them to open up the db and it asked for a password this time-which is EXACTLY what I am looking for it to do. So I thought I had it but someone then told me that changing that might not be such a great idea because people might be able to change it and then mess up the db. Although-I can't figure out any other way to make it work so I think I just might be going this route for now...
Does anyone have a comment on this whether it is a good route or not?
Thanks again for everyone's help! It is greatly appreciated!!! :-)
Jun 15 '07 #21

Denburt
Expert 100+
P: 1,356
I just found an add-in from Microsoft that might help. I haven't tried it but it is supposed to give you some assistance and allow you to check some what if scenarios.

http://support.microsoft.com/kb/235961
Jun 15 '07 #22

Expert 100+
P: 344
does anyone have an idea how i can check to make sure all that is set up properly? because i followed the directions on how to do it..so im pretty sure that is all right but is there a way to make sure it is all connected properly??
thanks!
Sorry for the delay in getting back, I was otherwise occupied.

When you open an access database, you are are always connected to an mdw file (normally the default on) as well as the mbd file.

The copy of Access on each PC holds the default mdw file for that PC. To change it for that PC you must open a database, any database, then (for Access 2003) go into the Tools-Security-Workgroup Administrator and join the mdw you want. In previous versions of Access the WorkGroup Administrator is a seperate program.

As this has to be done on each and every PC, I use the following instead.

Create a shortcut to your version of access, and then put this in the properties of the shortcut, using your own names of course

"C:\Program Files\MICROS~2\OFFICE11\MSACCESS.EXE" c:\Bissau\BissauCode.mdb /wrkgrp Z:\Bissau\Bissau.mdw

Then using this shortcut will ensure your database is opened with your mdw file.

You can also run this code inside the mdb to find out what mdw you are using

debug.print SysCmd(acSysCmdGetWorkgroupFile)
Jun 16 '07 #23

Post your reply

Sign in to post your reply or Sign up for a free account.