Hi everyone,
I'm on Alpha Five v9 and a couple months back I took out 4 memo fields from my primary table and put them into 4 new separate tables. There were some lag issues and it looked liked there was some corruption going. The database file appeared to be ballooning from 4 GB to around 20 GB every time I tried to back it up, rendering it unusable. I think this also happened upon database compression/packing.
After reading a few threads indicating that it is best to keep memo fields in separate tables if you don't want to lose all your data (correct me if I'm wrong), I went ahead and recreated tables, imported data and took the four memo fields. It currently has around 7,000 records.
All four links in the set are matched on the same key as all one-to-one relationships matching on first record, cascade changes, and always include record from parent.
For example
Primary_table *Indexes: Issue_Count, ASC, Include Unique only
-issue_count (auto-increment; audo advance after field filled; Skip set to True)
+20 other numeric/char/date fields
Child_table_bcc *Indexes: Issue_Count, Order by Issue_Count, Asc, Include All
Child_table_cc *Index: Issue_Count, Order by Issue_Count, Asc, Include All
Child_table_issue *Index: Issue_count order by Issue_count, Asc, Include All
Child_table_resolution *Indexes: Issue_Count1, Order by Issue_Count, ASC, All; Issue_count order by Issue_count, Asc, Include Unique only
Alpha5 automatically added that Issue_Count1 index at some point, and doesn't really allow me to delete it.
First issue: Why isn't the field rule working anymore now? The first two fields of Child_table_one and Child_table_two originally auto-populated in the form itself. However, after moving them to their own tables, the field rules don't appear to be working anymore. My only work-around for this was to add a set field value action in the OnEnter Form event to evaluate to the field expressions I had already in the table's field rules.
Second issue: Why are duplicate records being created and disappearing from the form? For Child_table_resolution, it appears that field data entered disappears from the form after saving, switching to a different record then returning to the same record. I checked the tables themselves, and the records are there. I don't quite understand why it disappears from the form itself. I tried adding more text to the field that went blank and it now appears to create another record in the child table with the same issue_count number and the new entry. It appears to be happening with Child_table_resolution table only. Perhaps it's a field rule?
Any clues on where things might have gone awry?
I'm on Alpha Five v9 and a couple months back I took out 4 memo fields from my primary table and put them into 4 new separate tables. There were some lag issues and it looked liked there was some corruption going. The database file appeared to be ballooning from 4 GB to around 20 GB every time I tried to back it up, rendering it unusable. I think this also happened upon database compression/packing.
After reading a few threads indicating that it is best to keep memo fields in separate tables if you don't want to lose all your data (correct me if I'm wrong), I went ahead and recreated tables, imported data and took the four memo fields. It currently has around 7,000 records.
All four links in the set are matched on the same key as all one-to-one relationships matching on first record, cascade changes, and always include record from parent.
For example
Primary_table *Indexes: Issue_Count, ASC, Include Unique only
-issue_count (auto-increment; audo advance after field filled; Skip set to True)
+20 other numeric/char/date fields
Child_table_bcc *Indexes: Issue_Count, Order by Issue_Count, Asc, Include All
- issue_count (char, width=6, user entered)
- memo_field (simple default expression, set default value to field expression at start of record)
Child_table_cc *Index: Issue_Count, Order by Issue_Count, Asc, Include All
- issue_count (char, width=6, user entered, value of field must be unique)
- memo_field_two (simple default expression, set default value to field expression at start of record)
Child_table_issue *Index: Issue_count order by Issue_count, Asc, Include All
- issue_count (char width=6, user entered, value of field must be unique)
- memo_field_three
Child_table_resolution *Indexes: Issue_Count1, Order by Issue_Count, ASC, All; Issue_count order by Issue_count, Asc, Include Unique only
- issue_count (char width=6; user entered, value of field must be unique)
- memo_field_four
Alpha5 automatically added that Issue_Count1 index at some point, and doesn't really allow me to delete it.
First issue: Why isn't the field rule working anymore now? The first two fields of Child_table_one and Child_table_two originally auto-populated in the form itself. However, after moving them to their own tables, the field rules don't appear to be working anymore. My only work-around for this was to add a set field value action in the OnEnter Form event to evaluate to the field expressions I had already in the table's field rules.
Second issue: Why are duplicate records being created and disappearing from the form? For Child_table_resolution, it appears that field data entered disappears from the form after saving, switching to a different record then returning to the same record. I checked the tables themselves, and the records are there. I don't quite understand why it disappears from the form itself. I tried adding more text to the field that went blank and it now appears to create another record in the child table with the same issue_count number and the new entry. It appears to be happening with Child_table_resolution table only. Perhaps it's a field rule?
Any clues on where things might have gone awry?
Comment