Help With File Size Limitations - Large Flat Files

[...lengthy description deleted...] > QUESTION: > > Does anybody have a suggestion as to what I could do at this point? > Might it be possible to redesign the DB file on the Psion 3a in such a > way so that this error wouldnt occur? Perhaps exporting the Psion DB > file as fixed length and writing code in MS Access to append column by > column? > > Please post responses publicly and to my email address if possible. > > Thanks in advance! > > ------------------------------------- > Cory Sandahl > Programmer/Analyst > University of Washington > sandahl@u.washington.edu You could store the data two independent databases: db1: visit-related information Patient No: Last Name: First Name: Sponsor Code: Case Mgmnt (Y/N): Date: Type: Time: Comment: __________________________________ db2: patient-related information Patient No: Last Name: First Name: Sponsor Code: Case Mgmnt (Y/N): Mother Name: Father Name: Other Fam Mems: : Phone: Address: : and then the user would perform the relation "in his head" from these two databases (NOT two tables in the same database, so you don't have to have any 1-m relationship). This would allow the "man in the street" to carry only real data, and no humongous empty records. There is some data duplication, but it's worth it for useability (is it?) You could join the data at the MS Access level for the management reports. This is not a good solution at all, but it seems you have not chosen a tool which supports one (the psion). Good luck, __________________________________________________________________ | Clem Akins Standard Disclaimers Apply | |Reynolds Metals Co, Alloys Plant "Climb High, Cave Deep!" | | Muscle Shoals, Alabama USA cwakins@leia.alloys.rmc.com | |________________________________________________________________|