Should you use an mde for a back end?

[Paul Ponzelli]

Does it make sense to use an Access mde file for the back end of a split
database?

I've noticed that when you're using the Linked Table Manager to link a front
end to a back end, the default extension in the Files of Type drop box only
displays mdb files, although it does offer an option to select All files.
So, what's the best practice with regard to back end databases?

Thanks in advance,

Paul

 

[Albert D. Kallal]

It really does not matter, and I see no advantage, since a mde is to strip
out source code, and you have none in the back end...

I do often put in a autoexec macro in the BE file, and if users click on
it, I give them a message that tells them they don't have persons, and then
quick the application.

However, this is no advantage here I can think of ....

 

[Rick Brandt]

Does it make sense to use an Access mde file for the back end of a
split database?

I've noticed that when you're using the Linked Table Manager to link
a front end to a back end, the default extension in the Files of Type
drop box only displays mdb files, although it does offer an option to
select All files. So, what's the best practice with regard to back
end databases?

Thanks in advance,

Paul

The only thing it does is prevent someone from adding a code-based object to the
file like a form, report, or module. If that is a concern then I guess it
doesn't hurt. In its normal role as a repository for your tables it makes zero
difference.

 

[Paul Ponzelli]

Ok - it doesn't sound like there's any point to saving the back end as an
mde file.

Thank you, gentlemen.

Paul