[AccessD] Was Test, now deals with DB backend

William Benson vbacreations at gmail.com
Wed Apr 10 20:21:42 CDT 2013


Jim and Mark thanks.

What line of vba code might compact an mdb back end when access.exe is not
present?
On Apr 10, 2013 11:03 AM, "Jim Dettman" <jimdettman at verizon.net> wrote:

>
>  in-line
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William Benson
> Sent: Wednesday, April 10, 2013 10:55 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Was Test, now deals with DB backend
>
> How do I build such a solution?
>
> Would this work:
>
> 1) create an empty .accdb file with Access. Publish it as accde.
>
> 2) uninstall Access so that I now mimic a machine without capability to
> open that file
>
> 3) write some vba code which connects to the accde using dao or ado.
>
> 4) write some create table scripts using sql
>
> 5) inject data using sql into the tables and then more sql for anslysis and
> data edits
>
>
>   YES.
>
>
> ....
>
> If all of the above works then that will be what I asked for an example
> of... an Excel front end to an access db backend that someone who has
> office but not office pro (ie, no Access) can use.
>
> My next question is can such a be be compacted...?
>
>
>   YES.
>
> My next question is can an mdb and or accdb be created usine Jet etc
> without EVER having Access.exe?
>
>   YES.
>
> 2) I don't have any machines at my disposal which are clean of the files
> Access installs.
>
> Should I build an mdb, or accdb... then uninstall Access. The use Excel and
> some code to connect to the tables inside the mdb? What makes the tables
> visible to Excel?
>
>   You don't ever need Access.  You can create a DB from anywhere as long as
> DAO or ADO and the Jet components are available.
>
> Jim.
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


More information about the AccessD mailing list