Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - skiwi

Pages: 1 ... 109 110 [111] 112 113 ... 118
Bugs and Issues / Re: Unicode support in EA
« on: December 08, 2009, 01:15:37 pm »

Bugs and Issues / Re: Unicode support in EA
« on: October 28, 2009, 12:31:50 pm »
Can you clarify that.
I am able to create, save, and retrieve unicode characters in linked RTF documents
(note this is using Jet4 and SQL server 2003)

Note that this doesn't apply to the element however!.

Bugs and Issues / Unicode support in EA - causes project integrity c
« on: October 13, 2009, 10:05:56 am »
In some cases the use of Unicode causes the project integrity check to fail, see the (not attached - grrr) image below

Bugs and Issues / Re: Unicode support in EA
« on: October 13, 2009, 10:00:23 am »
I have reported a number of Unicode ([ch257][ch275][ch299][ch333][ch363]) issues for EA 7.5 848 on Windows with SQL Server 2003.

These include
  • the spell checker issue
  • unable to read an ODBC connection that is named with a Unicode character)
  • odd behaviour where unicode data is entered in some fields (and subsequently lost)

I urge you to report any more you find.

Bugs and Issues / Re: Unicode support in EA - spell check
« on: September 28, 2009, 09:13:10 am »
There is still a problem with spell checking, the spell check dialogue box does not display unicode characters correctly (see previous illustration)
and certainly does not correct a word where the correction includes a unicode character.

Bugs and Issues / Re: Unicode support in EA
« on: September 28, 2009, 09:07:26 am »
As indicated in the answers and solutions above here is the solution from support
[size=10](actually here is a thought, make all the support answers available in a knowledgebase)[/size]

By default, the .EAP file format is a Microsoft Jet 3.5 (Access 97) database format.  For full support of Unicode text, use the Jet 4.0 (Access 2000) file format.

First, open "Tools | Options | General" and enable "Use JET 4.0".  If this option is not enabled, EA will not recognize JET 4.0 eap files.

  • Download the Jet 4.0 version of the EABase.eap file from the website:
  • Extract this eap file to your local machine
  • Run "Tools | Data Management | Project Transfer"
  • Perform an EAP to EAP transfer with your own file as the source and the jet4 eap file as the target.
  • Open the jet4 eap file and attempt to enter the characters you require.  Files should now save and open again without any data loss.

Alternately, if Microsoft Access 2000 or higher is available, use the 'convert database' feature in Access to upgrade the EAP file for this purpose (may need to rename file to .mdb and back to .eap when finished).

If you wish to make sure that all new .eap files created by EA use the Jet 4.0 format, replace the EABase.eap file in your EA install directory with the file in the file.

I can't help thinking though that a sensible default going forward (10+ years after access 97) in to support unicode out of the box.

Bugs and Issues / Re: Unicode support in EA
« on: September 24, 2009, 11:26:18 am »
Simon & KP, thankyou

Bugs and Issues / Re: Unicode support in EA
« on: September 23, 2009, 02:06:11 pm »
The *.eap was access 97 format.
We have access 2003 installed.

I compacted and repaired the database.
Then converted to Access2002-2003.

Is it possible to tell EA what version of Access to create new *.eap files for?


Bugs and Issues / Unicode support in EA- spelling example
« on: September 23, 2009, 12:52:22 pm »
In spell checker try to change aeiou to [ch257][ch275][ch299][ch333][ch363]

[highlight]note the way the unicode characters are displayed[/highlight]

after a click on the change button

[highlight]where did the unicode characters go?[/highlight]

Bugs and Issues / Re: Unicode support in EA
« on: September 23, 2009, 12:44:23 pm »
SO... if there's some intermediate code (yours or Sparx's) that's also mis-specifying the datatype, you'll get the effect you see.

All EAP files should be upgraded to at least ACCESS 2000 format running Jet 4.0.

Thanks, most helpful. We don't use triggers, stored procedures etc.
How do we upgrade *.eap files, or check to see what format they are currently are?

Bugs and Issues / Unicode support in EA - a package example
« on: September 23, 2009, 12:33:30 pm »
Create a view - note name ([ch257][ch275][ch299][ch333][ch363])

Saved - not name (still ok)

Click once on name to select - What happened to name !?

Bugs and Issues / Unicode support in EA
« on: September 23, 2009, 12:10:52 pm »
We use EA both against *.eap files and an SQL server repository.

We are having problems with unicode, eg in notes and in names.
For example in some cases we can enter the data, but it is not the same when retrieved
( eg [ch257] comes back as a)

Is it possible this is related to the underlying access DB, or the use of the Jet 3.5.

Note I am using Jet 4.0, but there still appears to be a problem.

Bugs and Issues / EA 856 - Doc Generation - bullets
« on: May 26, 2010, 02:59:40 pm »
I'm generating a document for the first time in EA 856, targeted for Word (2003).

None of the bulleted or numbered lines from notes show in the document.
The style for these lines is "11 pt, Left: 0cm; Hanging: 0.63 cm, After: 0.05 pt" for both bulleted and numbered.

Is this a general problem?
If not can anyone suggest where to look / fix it.

A related question is: why does EA force formatting in documents instead of relying on the styles (from normal.rtf)?

PS I edited every one of the notes fields and toggled the bulletted/numbered lines to ensure they had been created by the current build.

Bugs and Issues / Re: Labels on data object hidden
« on: May 14, 2010, 06:32:17 am »
Actually the message you were supposed to get from support was that your model is wrong and to fix it you should change your stereotyped class to a stereotyped artifact. We won't be breaking anyone's diagrams.
Here are the messages I got, verbatim, the highlighting is mine
I'm assuming that you're referring to the BPMN DataObject element. The BPMN profile extends the "Artifact" metaclass with the <DataObject> stereotype. It does not extend the "Class" metaclass. If you try to apply the stereotype to the wrong metaclass then the results will be undefined.

Anyway, having said all that, I have tried applying the shape script associated with the DataObject stereotype to a variety of different metaclasses (including Artifact and Class). They all show their name in a label which can be hidden, and they all have a "Show Labels" command which brings the hidden label back. So I don't think the fact that one is a class and one is an artifact is the cause of the problem.
Here's the problem: the shape script lookup for the main shape searches for stereotype without worrying what the extended metaclass is, but the lookup for the label shape searches for the stereotype and extension. It shouldn't make any difference, until somebody applies stereotypes to the wrong metaclass.

The fix is to make the main shape search stricter, which won't help you and will in fact remove the shape script from this one object - you will have to replace your stereotyped class with a stereotyped artifact. The fix is also likely to break a number of diagrams that are currently "wrong, but look how you want them to look".

I have passed the issue on for a decision on whether we fix or not. If we do it will be applied to a future release of EA.
In fact no suggestion to change my diagram was made by support,
not surprising since I had already diagnosed the issue.

The point of this discussion, and bug report was that, when I first raised this problem, a problem that had myself and my colleagues stumped, and was not obvious at all to others who helped in this forum,
was the anomalous and unexpected behaviour of an object in a diagram, with no indication from the tool as to what might be causing the problem, ie the name/label not to show.
Neither was there any indication in the Help documentation that there were cases where the "Show Label" context menu item might not be available.

Its clear to me that this is a bug, and it needs fixing.

Pages: 1 ... 109 110 [111] 112 113 ... 118