Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: Dorian Workman on September 11, 2008, 10:48:09 am
-
Is there a way to get the 'not equal' character [ch8800] (unicode 2260) to display on state transitions on a Statemachine diagram?
I copy/paste it in from Word, but once I close and reopen the transition property window, it turns into a question mark.
Thanks.
-
Sounds like you're currently running on a Jet 3.5 database. (The default for EA.)
Enable Jet 4 in the options dialog (http://www.sparxsystems.com.au/EAUserGuide/index.html?generalsettings.htm) and download the Jet 4 base model. (http://www.sparxsystems.com.au/bin/EABase_JET4.zip)
Transfer your existing model to that model (http://www.sparxsystems.com.au/EAUserGuide/index.html?performadatatransfer.htm) and you shouldn't have any problems.
-
And submit a feature request that Jet 4.0 become the default. I've got such a request going now, but more support is probably needed.
Perhaps if more of us bring this to Sparx' attention it will make it onto the hit list for an upcoming build.
-
That worked, thanks guys. I will submit a Feature request too.
What other benefits are there to using Jet 4.0?
-
Likely greater stability, perhaps better speed. And the Jet 4.0 engine is either still within extended support by MS or only recently obsolete.
I suspect without (solid) proof that you are a bit less likely to have some other problems if you convert projects to and from DBMS repositories.
-
Things were going well for a while, but now I'm starting to get this error popping up. Any ideas? Thanks.
DAO.Recordset [3022]
The changes you requested to the table were not successful becasue they would create duplicate values in the index, primary key or relationship. Change the data in the field or fields that contain the duplicate data, remove the index, or redefine the index to permit duplicate entries and try again.
-
I don't know for sure, but that error has been seen before.
Search the forum for the error string and see whether the results provide a quick answer.
Meanwhile make a backup copy of your project. Then...
You can try checking your project from the EA main menu with Tools | Data Management | Project Integrity Check. Another thing to try is Tools | Manage .EAP File | Repair .EAP File.
You should grab the updated base file for Jet 4.0 (http://www.sparxsystems.com/bin/EABase_JET4.zip). Make sure you save your original file, since the download is sometimes (rarely) out of date. If it seems to be out of date, sometimes all you need to do is export all the reference data from the old one and import it into the new.
David
-
Thanks David I'll try this.
One thing, when I transferred my model, the size of my EAP jumped from 300 to 500MB. Is that expected?
-
Regarding the size increase, you could try Tools | Manage .EAP File | Compact .EAP File to reclaim space lost to stale data that Jet is still holding on to.
Otherwise the size gain is probably the difference in representing your data in Unicode and what is required to leverage Jet 4's new features.
-
In Unicode strings, most characters take 2 bytes. [There are a very few exceptions where additional bytes can be used to construct a composite character.] In general this doubles the size of string fields, with a corresponding increase in the total data size.
-
Thanks for all the replies. I restarted my machine and the DAO.Recordset [3022] errors have not returned yet, fingers crossed.
-
In Unicode strings, most characters take 2 bytes. (There are a very few exceptions where additional bytes can be used to construct a composite character.) In general this doubles the size of string fields, with a corresponding increase in the total data size.
That would not be the case if the data was utf-8 encoded. (then most Latin cheracters have one byte, just special charatcers have more bytes). I suppose the 4.0 model would allow utf-8 encoding?
Otherwise, I'd really like to know why 4.0 is not the default model. The "Project transfer" task is soemthing taht feels very awkward.
-
I agree Project Transfer was awkward, and I have been getting these intermittent DAO.Recordset [3022] errors ever since (they did return after my restart, but less often).
The only reason I can see is that Sparx wants to keep the size of the EAP Files down?
-
For fun I did the same thing to a model of mine, and shortly got the "DAO.Recordset" error also. I'm not sure moving to JET4 is bug free. Or at least converting a database might not be. I'm back on the previous setting.
-
Glad it's not just me then. :)
I will log a registered user bug ticket, and post back here with Sparx's response.
-
considered using <> ?
-
The change to Jet 4.0 has worked well for me. The DAO Recordset errors I previously reported have not reappeared. Thanks for the thought though.