My Assistant
Site Message
(Message will auto close in 2 seconds)
  |
 Way to FORCE a database to only open in Access 2003?
|
|
 May 4 2006, 09:31 AM
Post
#1
|
|
|
Utter Access VIP Posts: 2,434  |
Is there any way to make a database file in such a way that when the user opens the database it can ONLY open in a given version?
Basically how can I prevent a database that I created in 2003 from being opened in version 10 or 9? I know I can make a shortcut icon, but I mean the actual database itself. Thanks! |
 |
 
|
|
May 4 2006, 09:32 AM
Post
#2
|
|
|
Utter A-fishin'-ado Posts: 17,723 From: Cincinnati, Ohio, USA . . . ><((((°> |
If you convert it to 2003 format, I don't think it CAN open in any other format. (Until ACC2007 comes out)
|
|
|
|
|
May 4 2006, 10:19 AM
Post
#3
|
|
|
Utter Access VIP Posts: 2,434 |
Hmm, then I have another question:
At work we have a database that is CONSTANTLY becoming corrupted, supposedly according to the DBA it is because users are opening it in OLDER versions of Access... so ? |
|
|
|
|
May 4 2006, 10:24 AM
Post
#4
|
|
|
Utter A-fishin'-ado Posts: 17,723 From: Cincinnati, Ohio, USA . . . ><((((°> |
Doubtful. More than likely they are all hitting the same copy of the DB at the same time. Is this DB split and do all users have THEIR OWN front end?
|
|
|
|
|
May 4 2006, 10:26 AM
Post
#5
|
|
|
Utter Access VIP Posts: 2,434 |
It is NOT split, which was the first thing I noticed when I looked at it.
I was actually wondering about ways this could be fixed so it does NOT crash in the way it does. However, I'm really not sure how to approach the DBA about it, but before I even do that I want to be SURE I know the error. |
|
|
|
|
May 4 2006, 10:27 AM
Post
#6
|
|
|
Utter A-fishin'-ado Posts: 17,723 From: Cincinnati, Ohio, USA . . . ><((((°> |
This is the most common and likely source of corruption. It MUST be split with each user having their own front end.
Fix this and your corruption issues should go away. |
|
|
|
|
May 4 2006, 11:16 AM
Post
#7
|
|
|
Utter Access VIP Posts: 2,434 |
Now WHY does it become corrupt because of this?
|
|
|
|
|
May 4 2006, 11:25 AM
Post
#8
|
|
|
Utter A-fishin'-ado Posts: 17,723 From: Cincinnati, Ohio, USA . . . ><((((°> |
Access was not built from the ground up to be a multi user app. Its just one of the "work-arounds" you have to do in a multi user environment. It also make it much easier to manage.
|
|
|
|
|
May 4 2006, 11:28 AM
Post
#9
|
|
|
Utter Access VIP Posts: 2,434 |
Now once a database is split thusly, does it allow the admin to go in there and make changes without bothering anyone else?
Provided those changes are for the front end only? Then you just roll out a new front end once your changes are in place? |
|
|
|
|
May 4 2006, 11:31 AM
Post
#10
|
|
|
Utter A-fishin'-ado Posts: 17,723 From: Cincinnati, Ohio, USA . . . ><((((°> |
Yup. The basic flow is to have a development MDB that is kept locally. When a new version is created, it is compiled into an MDE. This MDE is put on a network share. Anytime a MDE FE is opened, it compares itself to the FE in the share. If the versions are different, it copies the newer version down to the local PC.
There are many examples of AutoUpdating FEs in the Archives here at UA. |
|
|
|
 |
|
Jump To Forum:
|
Go to Top · Lo-Fi Version | Time is now: 20th June 2013 - 12:58 AM |