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

Griffiths, Richard R.Griffiths at bury.gov.uk
Thu Apr 17 08:55:54 CDT 2003


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
> 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 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
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
--------------------------------------------------------------------------------------------------------------------
This e-mail, together with any files transmitted with it, is
confidential and intended solely for the use of the individual to
whom it is addressed. If you are not the intended recipient, or
the person responsible for delivering to the intended recipient,
be advised that you have received this e-mail in error and that any
use, dissemination, forwarding, printing or copying of this e-mail
is strictly prohibited without liability on our part.

By responding to this e-mail it is accepted that your response 
may be the subject of recording/monitoring to ensure compliance 
with the Council’s ICT Security Policy

If you have received this e-mail in error please notify the sender.


More information about the AccessD mailing list