[NIFL-TECHNOLOGY:1003] Re: Looking for an Administrative database

From: DREWOMARK@aol.com
Date: Fri Apr 28 2000 - 13:58:07 EDT


Return-Path: <nifl-technology@literacy.nifl.gov>
Received: from literacy (localhost [127.0.0.1]) by literacy.nifl.gov (8.9.3/8.9.0.Beta5/980425bjb) with SMTP id NAA14951; Fri, 28 Apr 2000 13:58:07 -0400 (EDT)
Date: Fri, 28 Apr 2000 13:58:07 -0400 (EDT)
Message-Id: <b0.4663978.263b29cf@aol.com>
Errors-To: listowner@literacy.nifl.gov
Reply-To: nifl-technology@literacy.nifl.gov
Originator: nifl-technology@literacy.nifl.gov
Sender: nifl-technology@literacy.nifl.gov
Precedence: bulk
From: DREWOMARK@aol.com
To: Multiple recipients of list <nifl-technology@literacy.nifl.gov>
Subject: [NIFL-TECHNOLOGY:1003] Re: Looking for an Administrative database
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Mailer: AOL 4.0 for Windows sub 100
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Status: O
Content-Length: 1428
Lines: 26

Hi,

It sounds like you have someone there who knows something about access.  Have 
you considered redesigning the database in access.  You could export your 
current data to MS Excel (without losing the current database).  Tweak the 
data as needed in excel and then import it back into Access to your new 
database.  I'd test the new database design with a small sampling of the old 
data first to see if it worked the way you wanted.   

A lot of people are familiar with Excel (more than know access anyway) and I 
find excel easier to manipulate data in.  the number of records you have is 
one thing to consider as well as the number of current tables.  If you have 
multiple tables you'll need to be careful of the order of records.  if you 
don't have a really huge number of records and fields the simplest way to 
insure that they don't get scrambled might be to create a query that included 
the fields in all your tables and then export the query results.   
Wether you get a new program or not you're going to want to import your old 
data to the new database so you're going to have integrity issues no matter 
what.  It just seems like if you already have the program and people know how 
to use it, it might be easier to redesign and continue using it than 
retraining every one.  You'll need a new design anyway and you already know 
this software.

Good luck,
Adele Markert
Tech Coordinator St. Jerome School 



This archive was generated by hypermail 2b30 : Tue Jan 16 2001 - 14:45:29 EST