Simple ldb file question...
- Thread starter mjn015
- Start date
boblarson
Smeghead
- Local time
- Yesterday, 20:27
- Joined
- Jan 12, 2001
- Messages
- 32,059
Are people accessing the same mdb file on a network drive? If so, I would HIGHLY (and several other senior members here would agree) that you really should split your database to a Front-End/Back-End and have a separate front-end on each user's computer.
We had the same problem at my work when I first started here and I told them that they needed a front end on every workstation and they about choked because they didn't want to have to deal with installing one on everyone's workstation every time a modification was made to the front-end. So, I created the tool here:
http://www.access-programmers.co.uk/forums/showthread.php?t=111132
which allows you to enable auto-updating of front ends so users, and you, don't need to worry about having the latest release of the front-end.
We had the same problem at my work when I first started here and I told them that they needed a front end on every workstation and they about choked because they didn't want to have to deal with installing one on everyone's workstation every time a modification was made to the front-end. So, I created the tool here:
http://www.access-programmers.co.uk/forums/showthread.php?t=111132
which allows you to enable auto-updating of front ends so users, and you, don't need to worry about having the latest release of the front-end.
Len Boorman
Back in gainfull employme
- Local time
- Today, 04:27
- Joined
- Mar 23, 2000
- Messages
- 1,930
Agree with bob on FE at each user but does make update a problem without tool.
If only few users then use FE on server (which is generally my practice)
Important point is that users require full permissions. That is Read, Write,Modify and Delete. Without these you can get ldb file out of synch and hanging about when it should have gone.
Had this issue where I work and had to stamp my foot a bit, but they believe me now
L
If only few users then use FE on server (which is generally my practice)
Important point is that users require full permissions. That is Read, Write,Modify and Delete. Without these you can get ldb file out of synch and hanging about when it should have gone.
Had this issue where I work and had to stamp my foot a bit, but they believe me now
L
boblarson
Smeghead
- Local time
- Yesterday, 20:27
- Joined
- Jan 12, 2001
- Messages
- 32,059
Yeah, when I got here they were using a single MDE file on the network for every user (approx 100 users) so it was no wonder the db was getting corrupt every other day.
Len Boorman
Back in gainfull employme
- Local time
- Today, 04:27
- Joined
- Mar 23, 2000
- Messages
- 1,930
Obviously they had an Xspurt before you
Xspurt
X = Unknown quantity
spurt= drip under pressure
L
mjn015
Registered User.
- Local time
- Yesterday, 23:27
- Joined
- Apr 10, 2007
- Messages
- 29
Another Access question...
Bob & Len,
Thanks for your input on my post. Your thoughts have opened my eyes, so to speak. We are indeed, having multiple people accessing the same .mdb file on a network drive. I had never heard of Front-end/Back-end until your posts. I'm now also reading about converting my .mdb file into an .mde file. Of course, I've never worked with MS Access until now, so this is all new to me. Is there some sort of "cookbook" document you can recommend that will assist me in creating a front-end/back-end db from what I currently have now and/or converting from an .mdb to and .mde?
Thanks,
Michael
Bob & Len,
Thanks for your input on my post. Your thoughts have opened my eyes, so to speak. We are indeed, having multiple people accessing the same .mdb file on a network drive. I had never heard of Front-end/Back-end until your posts. I'm now also reading about converting my .mdb file into an .mde file. Of course, I've never worked with MS Access until now, so this is all new to me. Is there some sort of "cookbook" document you can recommend that will assist me in creating a front-end/back-end db from what I currently have now and/or converting from an .mdb to and .mde?
Thanks,
Michael
boblarson
Smeghead
- Local time
- Yesterday, 20:27
- Joined
- Jan 12, 2001
- Messages
- 32,059
I don't think there's any book I can suggest. However, here's a link:
http://www.databasedev.co.uk/split_a_database.html
You can also do some searching of the forum and look for posts on FE or Front-End, frontend, etc.
http://www.databasedev.co.uk/split_a_database.html
You can also do some searching of the forum and look for posts on FE or Front-End, frontend, etc.
mjn015
Registered User.
- Local time
- Yesterday, 23:27
- Joined
- Apr 10, 2007
- Messages
- 29
Hello Bob,
I am attempting to use your Auto-update utility, but I cannot get it to work properly. I've tried a number of times with different results for each, which only makes troubleshooting that much more difficult. Some of the things I've run into are:
1) One time I got a "Run-time error 3078"
2) One time it looked like it was going to work, but when it tried to update the mde, it would get in an endless loop and I had to delete the cmd file the code generated.
3) One time nothing at all happened even though I had different table versions that should have triggered the auto update.
4) One time it again looked like it was going to work, but the cmd deleted the old mde and then I got an error saying it was "missing".
I'm following your utility instructions, but I can't get it to work. One thing I noticed - In step 3 of 5 of your instructions, I'm instructed to find the 'tbl-version_master_location' table in my Back End, but that table is in my Front End and not my Back End. And...the correct location is already set. Could this be what's causing the utility to not work properly for me? I'm not sure what I'm doing wrong.
Help...
Thanks,
Michael
I am attempting to use your Auto-update utility, but I cannot get it to work properly. I've tried a number of times with different results for each, which only makes troubleshooting that much more difficult. Some of the things I've run into are:
1) One time I got a "Run-time error 3078"
2) One time it looked like it was going to work, but when it tried to update the mde, it would get in an endless loop and I had to delete the cmd file the code generated.
3) One time nothing at all happened even though I had different table versions that should have triggered the auto update.
4) One time it again looked like it was going to work, but the cmd deleted the old mde and then I got an error saying it was "missing".
I'm following your utility instructions, but I can't get it to work. One thing I noticed - In step 3 of 5 of your instructions, I'm instructed to find the 'tbl-version_master_location' table in my Back End, but that table is in my Front End and not my Back End. And...the correct location is already set. Could this be what's causing the utility to not work properly for me? I'm not sure what I'm doing wrong.
Help...
Thanks,
Michael
boblarson
Smeghead
- Local time
- Yesterday, 20:27
- Joined
- Jan 12, 2001
- Messages
- 32,059
Not sure why you would get this unless you set one of the paths wrong. The master location path should have the path with the backslash at the end but not the file name.
The master in the backend says one version but the mde master file says something else. Make sure that after you have made design changes to recreate the master mde file.
Not sure about that one.
Again it sounds like the master mde file wasn't there in the path it was looking for it.
Yes, a typo in the instructions.
can you post a screenshot of the table with the whole location showing?
mjn015
Registered User.
- Local time
- Yesterday, 23:27
- Joined
- Apr 10, 2007
- Messages
- 29
I've gotten to the point where I can consistently get the same error/issue to occur. I get the message that "Your program is not the latest version...." 
I click on OK and it looks like it updated the mde, but when I bring up the form, it again states "Your program is not the latest version...." This keeps happening over and over. 
I have to delete the UpdateDbFE.cmd file from my desktop to break out of the loop. I'm attaching a print screen of my table for the master location path.
I click on OK and it looks like it updated the mde, but when I bring up the form, it again states "Your program is not the latest version...." This keeps happening over and over. I have to delete the UpdateDbFE.cmd file from my desktop to break out of the loop. I'm attaching a print screen of my table for the master location path.
boblarson
Smeghead
- Local time
- Yesterday, 20:27
- Joined
- Jan 12, 2001
- Messages
- 32,059
Can you also give me a screenshot of the two version tables (from within the frontend)? Also, are you sure you are creating a new MDE file from the MDB file after changing the version numbers? I had that problem happening with exactly what you describe as I had changed the version numbers but forgot to make a new MDE file from that mdb after I did.
boblarson
Smeghead
- Local time
- Yesterday, 20:27
- Joined
- Jan 12, 2001
- Messages
- 32,059
Bob,
Picture if you will...heat rushing to my face...turning beet red...as I read your reply...Duh!! I wasn't creating a new MDE!!!
Don't feel too bad on that one. It took me quite a while to figure that one out when I did that myself
- Local time
- Yesterday, 22:27
- Joined
- Feb 28, 2001
- Messages
- 30,156
A fine point:
When setting Windows permissions on the .MDB file and the folder in which it resides, ...
When you right-click on the object to get properties, then follow that to the security settings tab, you see the "basic" permissions. You need MODIFY access to the folder. You do not need FULL CONTROL.
If you go "Advanced" from there, you need every permission EXCEPT "Take Ownership" and "Change Permissions." I don't think it matters whether you have "Read Permissions."
Don't forget that if your shared folder isn't a first-level folder, you will also need to have "Traverse Folder" on all parents and "List Folder" on the folder holding your DB. (You will need "Traverse Folder" on the MFD but usually this is allowed by default anyway.)
If your application involves child folders that Access will also travers, then you need to set up the folder first, then use Windows inheritance options to propagate the permissions to the child files and folders.
You MUST have "Create Files" and "Delete" on the folder contents. Your network security officer might wish to prevent you from having "Delete" on the folders themselves, but inheritance can be made to do this correctly.
Symptom: MDB comes up as though opened exclusively. Cause: You cannot create the .LDB file in the appropriate place, so you cannot share lock data. In that case, Access has no choice but to open the MDB exclusively.
If you aren't sure about what I just told you, get with your sys admin or network admin. They should understand what I'm saying here.
When setting Windows permissions on the .MDB file and the folder in which it resides, ...
When you right-click on the object to get properties, then follow that to the security settings tab, you see the "basic" permissions. You need MODIFY access to the folder. You do not need FULL CONTROL.
If you go "Advanced" from there, you need every permission EXCEPT "Take Ownership" and "Change Permissions." I don't think it matters whether you have "Read Permissions."
Don't forget that if your shared folder isn't a first-level folder, you will also need to have "Traverse Folder" on all parents and "List Folder" on the folder holding your DB. (You will need "Traverse Folder" on the MFD but usually this is allowed by default anyway.)
If your application involves child folders that Access will also travers, then you need to set up the folder first, then use Windows inheritance options to propagate the permissions to the child files and folders.
You MUST have "Create Files" and "Delete" on the folder contents. Your network security officer might wish to prevent you from having "Delete" on the folders themselves, but inheritance can be made to do this correctly.
Symptom: MDB comes up as though opened exclusively. Cause: You cannot create the .LDB file in the appropriate place, so you cannot share lock data. In that case, Access has no choice but to open the MDB exclusively.
If you aren't sure about what I just told you, get with your sys admin or network admin. They should understand what I'm saying here.
