Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Forms Programming / December 2005

Tip: Looking for answers? Try searching our database.

Access ODBC Driver for MDE

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
MBoozer - 01 Dec 2005 05:18 GMT
When you convert your app to an MDE, is there a special ODBC driver that is
needed for the Internet Information Server. When you look at the
administrative tools in control panel and look at the ODBC drivers, it says
ODBC driver for Access.mdb. Since you are converting to an MDE file, do you
need an Access.MDE ODBC driver or does the one for .mdb work?
david epsom dot com dot au - 01 Dec 2005 05:27 GMT
And if you go to France or Germany, it says something else again.

But it doesn't actually use Access, and it doesn't care what the
file extension is :~)

However, we wonder why you are converting a data file to an mde?

Converting an Access database strips out the text version of any
VBA code you may have written, and locks the Forms and Reports.
It does not do anything at all to the data in your tables.

You normally would not have any forms or reports in an ODBC data
source.

(david)

> When you convert your app to an MDE, is there a special ODBC driver that
> is
[quoted text clipped - 4 lines]
> you
> need an Access.MDE ODBC driver or does the one for .mdb work?
MBoozer - 01 Dec 2005 05:42 GMT
Thanks Dave. I want the MDE because we are going to be selling the database
and don't want the users to be able to see the code or more importantly, be
able to corrupt the code.

> And if you go to France or Germany, it says something else again.
>
[quoted text clipped - 20 lines]
> > you
> > need an Access.MDE ODBC driver or does the one for .mdb work?
david epsom dot com dot au - 01 Dec 2005 08:22 GMT
But why is there any code at all in a database with data in it?

At best that means you can't sell them an update without overwriting the
data.

We distribute MDE files, but all of the data is in a separate linked MDB (or
SQL Server).

(david)

> Thanks Dave. I want the MDE because we are going to be selling the
> database
[quoted text clipped - 17 lines]
>>
>> (david)
MBoozer - 01 Dec 2005 14:59 GMT
The app is for them to enter their "own" data. I figured in the future we
could offer an update as an MDE in whihc they would have to import the tables
or we could write a script that would do that?

> But why is there any code at all in a database with data in it?
>
[quoted text clipped - 27 lines]
> >>
> >> (david)
david epsom dot com dot au - 02 Dec 2005 00:32 GMT
Normally people distribute as two files: an MDE (which can be
placed on each workstation) and a linked MDB (which can be
placed on the network server). It's not the only way to do
it, but you need to think about what you are doing if you are
going to strike out on your own with your own approach :~)

If this is a small, non-networked, single-user application
then yes, distributing a single file now is a good idea, and
later you can provide upgrades by including a script to import
all the data.

(david)

> The app is for them to enter their "own" data. I figured in the future we
> could offer an update as an MDE in whihc they would have to import the
[quoted text clipped - 34 lines]
>> >>
>> >> (david)
MBoozer - 02 Dec 2005 05:40 GMT
Thanks Dave. I agree. But my distribution will be for network application
which means I should do be-fe. However, if I distribute as be-fe, then he
user has to do table linking and I'm not sure how that is done.

> Normally people distribute as two files: an MDE (which can be
> placed on each workstation) and a linked MDB (which can be
[quoted text clipped - 47 lines]
> >> >>
> >> >> (david)
david epsom dot com dot au - 09 Dec 2005 07:05 GMT
> user has to do table linking and I'm not sure how that is done.

Here are some examples:

How to relink back-end tables with the common dialog control in Access 2000
http://support.microsoft.com/?kbid=209862

Relink Access tables from code
http://www.mvps.org/access/tables/tbl0009.htm

> Thanks Dave. I agree. But my distribution will be for network application
> which means I should do be-fe. However, if I distribute as be-fe, then he
> user has to do table linking and I'm not sure how that is done.
>
>> Normally people distribute as two files: an MDE (which can be
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.