Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: R C Nesbit Newsgroups: comp.lang.basic.visual.misc Subject: Re: Getting inside an .accdb file Date: Wed, 23 Nov 2011 18:10:00 -0000 Organization: SpamTrap Lines: 26 Message-ID: References: <0oblc7pfk10v98r7ltis6332007vqcn43o@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: individual.net vlfquNrsqiSPy7RNlJcduQouDsoUzsng/RF4DyGwh8oBahmdU0 Cancel-Lock: sha1:fUsTU/c96ouRBopYIaNTY/byXT4= X-Newsreader: Virtual Access Open Source http://www.virtual-access.org/ Xref: x330-a1.tempe.blueboxinc.net comp.lang.basic.visual.misc:529 Tony Toews spoke: > >Indeed - and the original plonker who wrote the Access app (and charged a > >pretty penny for it, I might add) needed a good whack with a clue-stick. > >Basically a colletion of flat tables, absolutely no normalisation (e.g. a > >Customers table with a completely new record duplicating name address > >etc. for every additional contact at that customer) > >and worse, table names with spaces and table names like "11/ 09/11" > > Oooyyy! I'm not sure why I charge such reasonable prices. Nothing personal - I've developed lots of apps using Access - but only as a back-end database engine with a separate VB Executable front-end. It is perfect for small databases with limited users and record counts, and using a separate .exe front end the user doesn't have to have Access installed on every desktop. But we also use other RDBMS's, MySQL, SQL-Server etc. and migrating data from an Access file with spaces all over the place is a pain in the bum, to be honest. -- Rob Pearson