Migrating An Unnormalized Db To A New Normalized One...
Jul 25, 2006
Hello all...
How do you merge / append records from one database into another? The old database was very poorly designed (i.e. no normalization), but much of the data is the same.
Instinct from what I have learned says do this:
- create a query in each database that joins all fields together into a flat table
- run an update query that migrates the source data to the new database.
I really have no idea though, and to be honest... even if this is how it is done, I am very unsure how to proceed!
I hope that you understand me. Excuse me for the language failers. I am a common Dutch guy. I hope dat somebody can help me. I learned here already very much on this forum. I appreciate this very much.
We are upgrading our Access 97 databases in our company since we were told that Microsoft is, or will soon no longer, support A97.
I've migrated a few of our simpler databases already. Everything went without a hitch and all functionality was retained.
Word spread and now other depts are seeking my assistance. Some of these databases are somewhat complex in regard to their use of modules and linked/ODBC tables.
If I were to attempt to convert the 97 version (copy of course), and if anything were not to convert properly, would Access tell me in the form of an error message or table? Or do I have to manually test all functionality in the 2000 version and hope that I didn't miss anything?
We currently run Access 97 in the following way. We are looking for a solution where new members can access our data and change it using the internet. We are not sure of the best way.
Our database is split between "data" and "front-end". The "data" is kept on our win2000 server and is split into a "master" and several replicas. Some employees run their "front end" acceess programs on fixed computers attached to our network and simply attach to the "master" "data" database on our server. 4 employees use laptops and run their "fronends" by attaching to their own "replicas" of the "master" which they carry around with them. Once in a while, ususally daily, they synchronise their "replica" with the "master" on our server by simply attaching to our network using ethernet or WiFi.
What would be the best way to allow new members to join in the fun? There could be as many as 10 new members (brining the total to 16). The main problem is that they are located in different countries and ideally need to have a web or VPN access to our server. Does anyone have some suggestions? Should we migrate to SQL?
The database "data" is about 180Mb in size and has 40 odd tables that are used in a complex way by the "front ends". All queries are stored in the "front ends".
So I’ve been assigned to develop a database in Access which will house information on students who are participating in an internship program sponsored by my employer. I was given a spreadsheet with roughly 40 columns, so it is pretty detailed info about the students. For example personal student info (DOB, email, phone, etc), as well as school, major, year rank, school address, permanent address, etc.
Importing this given table is easy, just by using the import wizard. However I am faced with a challenge. The info I have is up to date at this point however in years to come there will be a need to import new student info. The only way my employer wants that to be done is by taking the new excel spreadsheet and importing that data into the already created database. Now this wouldn't be a problem if the DB is one flat, non-normalized, table because the columns would line up. However I feel that the DB needs to be normalized because of the vast amount of data that is repetitive, such as State or Major.
Is there a way to import an excel sheet into an existing normalized access database? Or even a way to automate it so that the excel columns would be broken up into the separate corresponding normalized tables?
I have a SharePoint list that tracks the date/time of each stop of an order from its origin to its destination. The number of stops varies depending on the type of order (you can use train as a metaphor). The goal is to calculate the average time between each stop (we're trying to figure out where orders typically get held up).
Let's say there are stops A, B, C, D, and E. Every order starts at A and ends at E. If they all made every stop, I could easily get the average of datediff("d", B, A) etc.
However, since they make different numbers of stops, what I need is the difference between the stop and the last stop they actually made. I need a crosstab query (or report) that lists the OrderType as the row, the StopName as the column, and the average(datediff) as the value.
In a perfect world, this would be normalized and I'd have separate tables for the stops and the order types, but trying to do that through SharePoint is Not Fun and is going to confuse the end users.
I have a fairly complete data model, my question is, how best to create tables for entry where I do not have subform after subform, and subforms in subforms. With subforms for the subforms and subforms on top of that.
I am about to start pulling out some teeth because at this point it sounds fun compared to this!
Do I need to use a query to base my table off of to build my Customer entry form? Or is my only option to use 15 frikin' Subforms? I I use a query, does that cause problems with data integrity?
I am having trouble finding useful reference to this, both online and in books I have purchased.
Normalization is fantastic, I understand.... But besides the crumby Northwind sample DB that everyone and their brother directs you to, is there an actual useful sample to look over that illustrates the use of a normalized data model?
I have grown more than a bit irritated with this, mainly because of my own inablilty to make progress in putting this project together.
I would like to create a simple to use, streamlined systems that promotes efficiency and speed, not a super convoluted system that has 85 subforms on every form in the DB.
I would REALLY appreciate some feedback/direction here, I am about to give up on normalized data and go with a simple flat table approach.
I would rather have redundant data than indecipherable forms that I have to answer incessant questions about.
I'm fairly new to Access, but have set up a database containing 8 normalized tables. I would like to know if it's possible to update all those tables by importing an Excel file into each table, or importing the Excel file into one Access table and then appending that table to those 8 tables. AND STILL MAINTAIN THE RELATIONSHIPS. The Help directory only talks about importing or appending into one table.
I have four tables with unique records as shown below. I'd like to add a record for a new item to the database by selecting the values from combo boxes for Supplier, Item and Unit. If the values do not exist the user would then type in a new value. SuppliersItemCode and Cost would always be new values. What's the best way to go about this? I am unsure how to add a record to a normalized database where you sometimes have to use / reference existing unique values in multiple tables via foreign keys for the new record.
The logic of the form would be:
1. Select existing or add new Supplier. 2. Select existing or add new Item. 3. Select existing or add new Unit. 4. Enter new SuppliersItemCode 5. Enter Cost
Okay - the other database is in the works and is going sloooow (the one that is being created with normalization).
Meanwhile, my other database that has no normalization I am having a problem running a query (now I know why its so important to have good structure).
To give you an idea on how bad this is...:o .....
3 tables - 94 fields to each table - each table has identicle fields, just different data. :eek:
Anyways, I have students in each table (each table is an Annual Report). I want to be able to run a simple query and combine all the students into one.
How would I achieve this?
Thank you!
And for all who are thinking about designing a database - READ READ READ and do some more reading on normalization!!!
