(See earlier post "Record Is Too Large")
This morning I just wiped out all earlier tables, kept the original tab
delimited table and Form, then went back in and did a complete new DB
split
and accepted all defaults. Got the thing split, fields changed to
date/time
& memo as appropriate, field sizes trimmed to reasonable numbers, and
saved
the work. Rebuilt the data entry/edit Form and insured that it was
pointing
to the newly created tables. Closed MSAccess and went back in and
everything worked perfectly! I then edited several records and
saved...again it worked perfectly. No 'record is too large', no err's at
all. Then I clicked on the Create New Record button, copied some text
from
another do***ent with a Ctrl-C and pasted it into a Memo field in one of
the
records...POOF, the entire DB now consists of a single empty record (which
AutoNumber refuses to create a record number for and which won't accept
any
data in any fields). All tables except for 3 were just gone. Closed
MSAccess and went back in, the remaining 3 tables were now gone along with
the Form.
This was just a simple DB with no macro's, no code, just a few tables and
one Form.
After hunting all around the system for the tables & form, I ended up
re-splitting (again) the original tab delimited table, again accepting all
defaults and letting the system create the new tables. After the new
tables
were created, went into the new tables in Design mode to edit the field
properties. Got the first few fields edited and then (surprise) got
"Record
is too Large". (!!!)
Can anyone at all tell me just what the <expletive deleted> is going on
here?!? I really don't want to spend another Entire Day repeating this
exercise if I'm missing something stupid and might end up having it
self-destruct again.
Jack
|
