Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Splitting a large database 1

Status
Not open for further replies.

jlockley

Technical User
Nov 28, 2001
1,522
US
When I first set my main database I intended to split it up, but I couldn't figure out how to enter into multiple tables from one form. Over the years it has grown to barely manageable proportions, and each time I attempt to split it up into multiple tables I run into the same problem.

I need to distribute about 230 fields into maybe 6 tables.
Newrolname with fields
Name (key)
Telephone


Newrolstyle
Name (key)
California

Newroltype
Name (key)
Restaurant

Newroldocuments (MB files)
Name (key)
References

and so on and so on.

Creating a datamodel with one to many or many to one relationship and using PDx tools to create a form allows me to enter only the information from the main table.

Using an expert to create a database with many tables causes the error message cannot find file c:/../pdoxusrs.lck
when attempting to save the model.

Clicking on OK I find the fields from the first table in the DM listed. Attempting to choose any of these fields brings the message: PeAryIndex out of bounds.

Where does the boneheaded mistake lie? Anyone know?







 
This should be a relatively simple thing, JL. Don't worry about saving the data model for now and don't use the expert. With that many fields, it might be wise to use a notebook object, with MROs for the different tables on each page. Link the tables manually in the data model of the form (it will save with the form). Secondly, when you structure the child tables, you should have a second field in the key. for example:

Newrolname (parent)
Name (key)
Telephone

Newrolstyle (child)
Name (key)
StyleNum (key)
California

Newroltype (child)
Name (key)
TypeNum (key)
Restaurant

Newroldocuments (child) (MB files)
Name (key)
DocNum (key)
References



That second field in the composite key makes the record unique. If your existing fields (restaurant and references above) would make each record unique if keyed, you can omit my suggested names and just key them.



Mac :)

"There are only 10 kinds of people in this world... those who understand binary and those who don't"

langley_mckelvy@cd4.co.harris.tx.us
 
Thank youl I wiss try it and get back.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top