MDB to MDE Conversion

[Ray Stantz]

Good Day! Anyone know a reason why VBA procedures would stop working once a database is converted from a .mdb file to a .mde file? I thought the only difference in the two formats is the .mde will not allow changes to the design.

Thanks!

 

[Pauldohert]

Maybe you could post a procedure that no longer works, to see if someone can spot something.

 

[boblarson]

Also, one other thing to suggest is to just import all of your objects into a new mdb file and set your startup options, etc. and then try. Sometimes that will help.

 

[Ray Stantz]

Maybe you could post a procedure that no longer works, to see if someone can spot something.

One of the issues is with a button i have on a form the will pull up report based off the ID, which is the PK. The button is tied to an option group (check boxes) and you can either choose to preview the report or print it. The button has a module on the OnClick procedure that triggers this action.

The problem with the mde file is ff the form fileds are completly filled out, the report will display with all the associated information for that particular record. but if i leave a field blank, the database shuts down completely without an error message. In the mdb file the report displays regardless, it will just leave those particular fields blank.

Function letter2(F As Form)
If Forms![Site Visits]!Printtype = 1 Then
DoCmd.OpenReport "SVBOLetter", A_NORMAL, , "[id] = forms![Site Visits]!to"
Else
DoCmd.OpenReport "SVBOLetter", A_PREVIEW, , "[id] = forms![Site Visits]!to"
End If
End Function

 

[boblarson]

The problem with the mde file is ff the form fileds are completly filled out, the report will display with all the associated information for that particular record. but if i leave a field blank, the database shuts down completely without an error message.

That's why with an MDE you need to make sure to have error handlers in place. You can put an error handler in that event so that it will display a message and not kill your runtime app. If you do that and just put a message box with the error description and error number, you can then see what is occuring in the mde.

 

[Ray Stantz]

Thanks boblarson, i'll try both of your suggestions. I appreciate the quick responses from all.