![]() If your dev code goes wrong you are liable to lose recent data. AND don't mix dev stuff with data entry (like I do sometimes). Even so, there can be issues so frequent backups are the way to go. I only use AOO base for data entry, most of my procedures and functions are written in HSQL. So there are two things to consider if any of the sys engineers from AOO happen to be passing at the moment. But this may well be an unexpected side-effect of poor memory management because in the past (IIRC !!) I have upped the memory in the java start command. I believe the term "thread-safe" would be a desirable aim if my guess is correct. If the wrong one gets there first you can have a problem. That term applies to two parallel processes which do not synchronise but should. My belief is that there is a race condition which, whether or not it's that, is most prevalent at startup (opening calc or base).
0 Comments
Leave a Reply. |