mde vs. mdb - was RE: [AccessD] Secured vs. Unsecured FEs

Richard,

Anything that requires you to go into design mode cannot be done with an
.mde since there is no design mode in it.  If you need to make a
modification to a form or report, you have to do it to the .mdb and then
create a new .mde.

For my clients, I let them test using an .mdb that I can modify.  When
they are satisfied with it, I produce the .mde for production.

Charles Wortz
Software Development Division
Texas Education Agency
1701 N. Congress Ave
Austin, TX 78701-1494
512-463-9493
CWortz at tea.state.tx.us



-----Original Message-----
From: Griffiths, Richard [mailto:R.Griffiths at bury.gov.uk] 
Sent: Thursday 2003 Apr 17 08:56
To: 'accessd at databaseadvisors.com'
Subject: RE: mde vs. mdb - was RE: [AccessD] Secured vs. Unsecured FEs


Thanks, I know its not possible to create references on the fly but what
other things cannot be done? Richard

> -----Original Message-----
> From:	Wortz, Charles [SMTP:CWortz at tea.state.tx.us]
> Sent:	17 April 2003 14:37
> To:	accessd at databaseadvisors.com
> Subject:	mde vs. mdb - was RE: [AccessD] Secured vs. Unsecured
FEs
> 
> Richard,
> 
> If you create an .mde then you must, repeat MUST, keep the .mdb it was

> created from.  The .mdb has all the human-readable code, the .mde has 
> only compiled machine-readable code in it.  Thus, you cannot make 
> changes in the .mde unless you like bit-twiddling or have a product 
> that can reverse-engineer the .mde.
> 
> Charles Wortz
> -----Original Message-----
> From: Griffiths, Richard [mailto:R.Griffiths at bury.gov.uk]
> Sent: Thursday 2003 Apr 17 03:07
> To: 'accessd at databaseadvisors.com'
> Subject: RE: [AccessD] Secured vs. Unsecured FEs
> 
> Further to this debate - are there any drawbacks/limitations or 
> important considerations concerning functionality to take into account

> when using an mde?
> 
> Richard