Does CC somehow store a view of the table structure when it first encounters a table? Because I'm having some issues that seem to indicate that.
In some cases, I've renamed fields or reworked table structure, and then modified my CC and CF stuff to match the new format. But then I get SQL errors where it's complaining that the initial field doesn't exist (even though there are no reference to it in the CC Model or the CF fields).
In other cases, I've created a CC against a table, then decided I needed more fields, and the CC doesn't pull the new fields. I CAN list the fields in the "Field" portion of the CC model and it will pull them there. But then there was other weird behavior.
How can I reset the CC expectation of the structure, so that it will automatically pull all of the current fields?
In some cases, I've renamed fields or reworked table structure, and then modified my CC and CF stuff to match the new format. But then I get SQL errors where it's complaining that the initial field doesn't exist (even though there are no reference to it in the CC Model or the CF fields).
In other cases, I've created a CC against a table, then decided I needed more fields, and the CC doesn't pull the new fields. I CAN list the fields in the "Field" portion of the CC model and it will pull them there. But then there was other weird behavior.
How can I reset the CC expectation of the structure, so that it will automatically pull all of the current fields?
Hi farmington,
ChronoForms and CC both cache the table info for 24 hours. If you make changes please click the Delete Cache icon in the toolbar to refresh the records.
Bob
ChronoForms and CC both cache the table info for 24 hours. If you make changes please click the Delete Cache icon in the toolbar to refresh the records.
Bob
OMG, it's just that easy. I wish I had noticed that button earlier! It would have saved me a lot of frustration! Thanks a lot.
Hi farmington,
You are excused - the name does not make it obvious what the button does :-(
Bob
You are excused - the name does not make it obvious what the button does :-(
Bob
Yes, and I generally avoid buttons labeled "Delete" when I'm working with databases, unless I'm sure I know what it's going to do!
🙂
🙂
This topic is locked and no more replies can be posted.
