unable to create mde

  • Thread starter Thread starter Richardson
  • Start date Start date
R

Richardson

I have a database split into FE/BE with user level security in place. I am
logged as owner of all objects and have full permissions on everything. I
would like to convert the FE to .mde to protect the code that is in it.
However, when I got to the menu, the make mde is grayed out.
I tried it on an earlier version of my program with no security and no split
to a backend and the situation is the same. I am using Office XP developers
on an XP Pro machine.

Any thoughts?
Lori
 
Hi Lori,

Most likely this is because your Access 2002 database is using the default 2000 format.
You would need to convert the database to 2002 format in order to create an MDE using Access 2002.
Or use Access 2000 to create an MDE in 2000 format.

Here is a recent post by MVP Cheryl Fischer on this subject:
Two possibilities come to mind:

1. There may be coding errors in the database; these will prevent the
creation of an MDE. Open any code module and, from the VBA
menu, select Debug, then Compile. If there are any errors, you will see an
error message and the problem line of code will be highlighted. Continue
compiling until the compile completes with no messages at all.

2. If you are using Access 2002 or 2003, the default database format is
Access 2000. Unfortunately, if you use the Access 2000 database format in
Access 2002/3, you cannot create an MDE. You may only create an MDE of an
Access 2000-format database using Access 2000.[/QUOTE][/QUOTE][/QUOTE]

Hope that helps,
 
Check the format of the mdb(look at the title bar of the database window) -
Office 2002 used 2000 format by default. You need to convert it to 2002
(Tools menu), compile and save, and then try to make the mde.
 
Thank you. It is in the 2000 format.

Jeff, here's another question for you. In a message earlier, you indicated
that you had a button in your front end dbase that copied the backend and
date stamped it. Would you mind sharing the information about how you did
that?
I am concerned about the stability of a machine where my application will
be installed and I would like to have the backend backed up to a removable
device every 10 minutes when they are logged onto the system. The users
will not be logged on very often, but it is very heavy data entry when they
are.
You have a been a great help with all my questions.

Lori

Jeff Conrad said:
Hi Lori,

Most likely this is because your Access 2002 database is using the default 2000 format.
You would need to convert the database to 2002 format in order to create an MDE using Access 2002.
Or use Access 2000 to create an MDE in 2000 format.

Here is a recent post by MVP Cheryl Fischer on this subject:

Two possibilities come to mind:

1. There may be coding errors in the database; these will prevent the
creation of an MDE. Open any code module and, from the VBA
menu, select Debug, then Compile. If there are any errors, you will see an
error message and the problem line of code will be highlighted. Continue
compiling until the compile completes with no messages at all.

2. If you are using Access 2002 or 2003, the default database format is
Access 2000. Unfortunately, if you use the Access 2000 database format in
Access 2002/3, you cannot create an MDE. You may only create an MDE of an
Access 2000-format database using Access 2000.
Click to expand...
[/QUOTE]

Hope that helps,
--
Jeff Conrad
Access Junkie
Bend, Oregon

Richardson said:
I have a database split into FE/BE with user level security in place. I am
logged as owner of all objects and have full permissions on everything. I
would like to convert the FE to .mde to protect the code that is in it.
However, when I got to the menu, the make mde is grayed out.
I tried it on an earlier version of my program with no security and no split
to a backend and the situation is the same. I am using Office XP developers
on an XP Pro machine.

Any thoughts?
Lori
Click to expand...
[/QUOTE]
 
Richardson said:
Thank you. It is in the 2000 format.

I am concerned about the stability of a machine where my application will
be installed and I would like to have the backend backed up to a removable
device every 10 minutes when they are logged onto the system.
Click to expand...

You cannot backup or copy a database while someone has it open.
 
Hi Lori,
Thank you. It is in the 2000 format.
Click to expand...

Good to see you have the MDE problem resolved.
Jeff, here's another question for you. In a message earlier, you indicated
that you had a button in your front end dbase that copied the backend and
date stamped it. Would you mind sharing the information about how you did that?
Click to expand...

If you're referring to the post about having a customized login screen for a secured database,
sure, here is the exact code behind the button:

' Code Start
Private Sub cmdMakeBackups_Click()
On Error GoTo ErrorHandler

Dim strFileName As String
Dim strFileNoExt As String

strFileName = "C:\Bo$$97\Data\Data.mde"
strFileNoExt = "C:\Bo$$97\Backup\Data"

If MsgBox("Ready to backup the data files?", vbInformation + vbYesNo _
+ vbDefaultButton2, "Backup Data") = vbYes Then
FileCopy strFileName, strFileNoExt & Format$(Date, "mmddyy") & ".mde"
MsgBox "Backup complete. Please make sure to backup this file to a disk, " _
& "CD-ROM, or network directory on a regular basis.", vbInformation, _
"Backup Successful"
End If

ExitPoint:
Exit Sub

ErrorHandler:
If err.Number = 76 Then
MsgBox "The Backup folder is missing. Please call tech support " _
& "to report this error.", vbCritical, "Backup Folder Missing"
Resume ExitPoint
End If

If err.Number = 70 Then
MsgBox "The backup cannot proceed since the data files are currently " _
& "being used. Please exit completely out of the program before " _
& "continuing.", vbExclamation, "Cannot Proceed"
Else
fncErrMessage err.Number, err.Description
End If
Resume ExitPoint

End Sub
' Code End

What this does is copy the BE database called "Data.mde" from the folder
"C:\Bo$$97\Data" to a folder called "C:\Bo$$97\Backup."
It names the file with the current date. So if I was to run this today, the
resulting file would be called Data041304.mde in the Backup folder.
It works very nicely and I can easily see what day the backup was completed.

My error handling code catches the possibility of the Backup folder not existing and stops.
(At some point I'd like to change that to actually create the Backup folder if needed. That
will be a post of my own I'm sure!) I also stop the process if the file is being accessed.

I do this from a customized login screen in a second unsecured database. Since this second
database does not have any links to the main BE, this scenario works quite well for me.
I am concerned about the stability of a machine where my application will
be installed and I would like to have the backend backed up to a removable
device every 10 minutes when they are logged onto the system. The users
will not be logged on very often, but it is very heavy data entry when they
are.
Click to expand...

**Important Notes**
As pointed out in that earlier thread, this is for a SINGLE workstation setup!
I would NOT do this procedure on a multi-user situation, which it sounds like
your situation. No users can be using the BE tables and corruption could also happen as well.
**

Also, you mention that you want backups every 10 minutes. This sounds like VERY
important, mission-critical data!! If that's the case you may want to seriously think
about SQL Server for the BE tables as SQL Server has much better backup procedures.

As Joan pointed out, you cannot backup the BE if any users are accessing the file.
You would need to make sure each user is logged off and/or log them off when
you want to run the backup. If you wish to read more about this procedure I suggest
the following links/samples for study. I don't have any experience with this task myself,
but see if these links help. Watch out for any possible line wrapping on these links!

http://www.datastrat.com/Download2.html
Look for KickEmOff2K sample database.

http://www.rogersaccesslibrary.com/download2k.asp?SampleName='LogUsersOff2k.mdb'

http://www.rogersaccesslibrary.com/download2k.asp?SampleName='LogUsersOffNonUse2k.mdb'

http://support.microsoft.com/?id=198755

http://support.microsoft.com/?id=285822

http://www.candace-tripp.com/_pages/access_downloads.asp
Look for Detect and Logoff Idle Users
You have a been a great help with all my questions.
Click to expand...

You're very welcome.
 
Thanks again.
I am interested in using SQL for the BE tables, but my client is going to
using this application on an old hand me down machine, running Access
runtime because they won't invest in upgrading software or hardware. I want
to backup that often because of my fears about their system and because they
would have no idea what to do if the system went down. They also wouldn't
have another means of recreating the data.

I have found a workaround to the database being open. It isn't a full
backup, but I have it set to copy the 3 critical tables from the database to
a duplicate database on a jump drive. The tables are already set to archive
periodically, so I shouldn't be copying more than 200 records at a time. I
have one user who is capable of exiting and creating a backup copy from
Windows Explorer for the rest of the data.

If you see a problem with this workaround, please let me know.

Lori
 
Hi Lori,
Thanks again.
I am interested in using SQL for the BE tables, but my client is going to
using this application on an old hand me down machine, running Access
runtime because they won't invest in upgrading software or hardware. I want
to backup that often because of my fears about their system and because they
would have no idea what to do if the system went down. They also wouldn't
have another means of recreating the data.
Click to expand...

Understandable, but I still just question the every 10 minute thing. I don't mean any
disrespect, but that just seems like overkill. So if everything went down you would lose
at most only 10 minutes of data; that's it. How much data can the users possibly be entering
in only 10 minutes?! Entering thousands of records for that time span I would say, "OK,
that sounds reasonable", but wouldn't several hours of lost data still be *reasonable*
if only a couple of users are entering a few records in that time span?

Can you give us some idea on:
1. How many users are going to be using this database?
2. Will the BE be on a server and each have their own FE on their workstation?
3. What type of data are you entering? What is the business?
4. How many records are being entered/changed in a 10 minute time span?

Answers to those questions may help us better understand your situation.
I have found a workaround to the database being open. It isn't a full
backup, but I have it set to copy the 3 critical tables from the database to
a duplicate database on a jump drive. The tables are already set to archive
periodically, so I shouldn't be copying more than 200 records at a time. I
have one user who is capable of exiting and creating a backup copy from
Windows Explorer for the rest of the data.
Click to expand...
If you see a problem with this workaround, please let me know.
Click to expand...

I sense a major disturbance in the Force here!

Can you explain HOW you are copying 3 critical tables from database to the other?
If you are copying a table that someone is accessing you are at grave risk for data corruption.
I'm completely lost when you say you are "archiving" tables periodically.
This must be something you set up, because Access does not have anything like this
out of the box. How are you archiving the data and how are you getting only around
200 records at a time?

I'm really not an expert in this area of Access so if you give us more details on your setup
I'm sure someone else can jump in and offer some concrete advice on how to proceed.
One idea off the top of my head is to have all unbound forms and through code write the data
to two separate databases whenever you need to create/change records. That would require
a LOT of coding to work seamlessly and even then it still may not work properly!
 
My bet is that the 10 minute thing derives from the fact that they "have no
means of recreating the data".

It sounds to me like they are taking orders over the telephone - on an old
machine, that is apparently likely to blow up on a regular basis, with no
commitment to suitably upgrading hardware or software, and no documented
procedures for what to do if the system goes down!

No thanks. Next job please!

Cheers,
TC
 
My thoughts (and fears) as well TC!

The Force is telling me "Lots of support calls for you
Lori!"
 
You are both right about the support calls, I am afraid. Unfortunatly, I am
committed and it is more than a job, it is for an organization I am
associated with personally. I just cross my fingers that I can suitably
setup restore procedures for the first crash and then I can use it as a
reason to get them to upgrade to a more stable environment.

Have a good day,
Lori
 
Well I don't envy your position then Lori.
Keep your fingers crossed that they never have a meltdown.
I would seriously talk with the "powers-that-be" about whether they
can afford NOT to upgrade! Explain to them (with numbers) how much
business could be lost by losing critical data with an unstable system.
How about bad publicity as well?

You may want to keep this link handy.

Database Recovery:
http://www.pksolutions.com/

Best of luck to you.

--
Jeff Conrad
Access Junkie
Bend, Oregon
Install the latest Windows Updates:
http://www.microsoft.com/security/security_bulletins/200404_windows.asp
 
Back
Top