A solution (plus three modules) was exported (via Servoy repository) from the main development computer, then imported into a laptop for a demo. All of the usual default options were selected. Upon opening the updated solution on the laptop, several connections seemed to be lost. For example, a few buttons that were connected to methods with onAction properties showed no such link after import.
What might cause de-linking of methods after export and import of a Servoy solution? Or, on another export/import, a relation was lost (it still existed, but the parameters were missing, causing an error at startup). Each time there is an export/import, it seems that different “damage” may occur.
Using MySQL 5.0.4, Navicat 6.3.3, Servoy 3.0.1, OSX 10.4.8.
Source computer 2 GHz G5 iMac, destination 2.16 Ghz Intel MBP.
Can’t say that I have ever come across this behaviour before.
It sounds as though the resulting errors are never consistent - that is, is it always the same onAction and relationship params and is it therefore reproducable after each export !?
Are there any differences between the MySQL database schema on your dev machine versus the demo machine ?
How about deleting the Servoy solution and dropping the database on the demo machine and recreating it afresh without any structure and then let the import create the solution and necessary tables at time of import - a sort of process to get the two in sync !?
What is consistent is that something would be affected. It does seem to be different each time.
The mystery for me is that 99+% of the methods that are connected to buttons stayed that way; just a few (generally more recently-assigned) buttons lost their method assignments.
I have downloaded a fresh copy of Servoy, installed it and transferred data for both databases (‘my_data’ and ‘repository_server’) via Navicat. Seems okay with respect to the disconnection issue.
What will be interesting is whether problems arise again upon importing modules that have been worked on remotely.