[AccessD] Split database conceptual problems

One further step is to rename GreenWorldNursery_data.mdb to 
GreenWorldNursery_data.dat and then relink.  That way they can't open the data file by 
double clicking on it.

Then explain that the .dat file contains the data and the .mdb/mde file contains the program 
that uses the data.



On 3 Jul 2009 at 15:53, Steve Schapel wrote:

> Doug,
> 
> I don't think I would ever have attempted to explain anything about the 
> files to any client.
> 
> I always install an application with a desktop shortcut, and as far as the 
> users are concerned, that's the only way to run the app.
> 
> I usually have a button on a form with code to zip up the backend database 
> and upload it by FTP to my server.
> 
> My frontends would always be MDE or ACCDE files, so I guess that would help 
> to distinguish from a backend MDB or ACCDB - provided they don't have 
> filename extensions hidden.
> 
> Not a complete answer, I know, but just a few related thoughts.
> 
> Regards
> Steve
> 
> 
> --------------------------------------------------
> From: "Doug Steele" <dbdoug at gmail.com>
> Sent: Friday, July 03, 2009 3:38 PM
> To: "Access Developers discussion and problem solving" 
> <accessd at databaseadvisors.com>
> Subject: [AccessD] Split database conceptual problems
> 
> > Hello All:
> >
> > All my client databases have a FE/BE structure.  I generally name the 
> > files
> > something like 'GreenWorldNursery.mdb' (FE) and 
> > 'GreenWorldNursery_Data.mdb'
> > (BE).  I send new clients a nice description of how FE/BE works, and 
> > always
> > explain at length on the phone or in person.  Over the years, however, 
> > I've
> > realized that about half the people I deal with seem to be unable to grasp
> > the concept of a front end with screens, reports, etc. and a back end 
> > which
> > contains only data, no matter how often I explain. Despite my best 
> > efforts,
> > they try to start the database by double clicking on the BE, copy the BE 
> > to
> > their local computer instead of the FE, send me back a copy of
> > 'GreenWorldNursery.mdb' when they have a data problem and I've asked them 
> > to
> > send me 'GreenWorldNursery_Data.mdb', etc. etc.
> >
> > I've solved the worst problems with code - my BE databases have warning
> > screens that show when they're opened; my FEs have all kinds of checks to
> > make sure they're not running off the server, are linking correctly to the
> > proper BE, etc.  But I spent half an hour today on the phone with a fairly
> > intelligent user who, it finally turned out, had confused the two files 
> > and
> > was reading me the WRONG FILE NAMES off her My Computer window.
> >
> > With that preamble, here are my two questions:
> >
> > 1. Has anyone come up with a good metaphor for explaining the difference
> > between a FE and BE .mdb file?
> > 2. Are there better naming conventions out there?
> >
>  
> 
> 
> __________ Information from ESET Smart Security, version of virus signature database 4211 (20090702) __________
> 
> The message was checked by ESET Smart Security.
> 
> http://www.eset.com
> 
> 
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com