I have a really odd event.
The application has 30 tables.
Some tables are Lookups.
The main Form had 4 tabs, Tab 2 was redundant and Tab 3 had complex image presentation actions. Tabs 2 and 3 were removed.
Tab 1 is the main data entry tab.
Field 10 has a lookup from a lookup table with a filter (Active = Yes, for example, which changes to No if the value has been used via an Update operation ). Any data can be entered here so it's not forcing a closest match.
Problem. Field 10 had been working and updating the lookup table. Then it stopped working.
On examining the tables, I found that there were 2 tables with the same structure;
Content and Content0 - the 0 is significant.
Content0 now had the Operation processing attached to it as I verified by dropping that table and seeing the operation disappear. On replacing the table, the operation returned, as expected.
Content has no Operation processing attached to it now.
Question. Under what circumstances does Alpha duplicate or rename and duplicate a table and also under what circumstances does the code get moved to the duplicated table?
On the face of it, it appears that the original table was renamed to Content0 while keeping the Content table with no processing.
My solution pending further comment from the Forum was to use the Content0 as the primary lookup and source of the update operation.
Now it works as before but I have the two tables Content and Content0. If this happened big style, it would wreck the application.
The application has 30 tables.
Some tables are Lookups.
The main Form had 4 tabs, Tab 2 was redundant and Tab 3 had complex image presentation actions. Tabs 2 and 3 were removed.
Tab 1 is the main data entry tab.
Field 10 has a lookup from a lookup table with a filter (Active = Yes, for example, which changes to No if the value has been used via an Update operation ). Any data can be entered here so it's not forcing a closest match.
Problem. Field 10 had been working and updating the lookup table. Then it stopped working.
On examining the tables, I found that there were 2 tables with the same structure;
Content and Content0 - the 0 is significant.
Content0 now had the Operation processing attached to it as I verified by dropping that table and seeing the operation disappear. On replacing the table, the operation returned, as expected.
Content has no Operation processing attached to it now.
Question. Under what circumstances does Alpha duplicate or rename and duplicate a table and also under what circumstances does the code get moved to the duplicated table?
On the face of it, it appears that the original table was renamed to Content0 while keeping the Content table with no processing.
My solution pending further comment from the Forum was to use the Content0 as the primary lookup and source of the update operation.
Now it works as before but I have the two tables Content and Content0. If this happened big style, it would wreck the application.
Comment