Book a Demo

Author Topic: incorrect created date  (Read 4978 times)

thoms005

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
incorrect created date
« on: November 08, 2002, 11:57:28 am »
I created a Use Case diagram with the Eval version and then 2 days later bought EA Professional Ed. I now open my orginal project in EA Pro and the Diagram Properties (that show on the Diagram Properties Note) list the Created Date as 12-Feb-2001. How can I change this? I clearly cannot give this diagram to the client with that date.

Please help!!

Thanks,
Carol

gsparks

  • EA User
  • **
  • Posts: 325
  • Karma: +0/-0
  • I love YaBB 1 Gold!
    • View Profile
Re: incorrect created date
« Reply #1 on: November 10, 2002, 06:31:00 pm »
There is no easy way to change this in EA; the created date is considered a 'set once' field. Regrettably the example diagrams in the base model are set to the date you mention.

If you have a copy of MS Access (97 or better) you can open the .EAP file and modify the CreatedDate and ModifiedDate fields in the t_diagram table. Ctrl + ; while in the date field can be used to insert the current date.

It would also be possible to export to XML, modify the date and re-import - but this is more work.

I hope this helps,

Geoff Sparks

thoms005

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
Re: incorrect created date
« Reply #2 on: November 11, 2002, 07:22:16 am »
Thanks Geoff, changing it in Access worked.  (even though I got a message when I opened the .EAP file that I couldn't save unless I converted it to Access 2000 since I was using 2000. That must have meant changes to the DB structure not the data itself. Threw me off at first).

Carol

James

  • EA User
  • **
  • Posts: 25
  • Karma: +0/-0
    • View Profile
Re: incorrect created date
« Reply #3 on: November 15, 2002, 05:05:26 am »
And if you don't have MS Access, you can do it in Excel (get external data via MS Query, connect to the Access database through ODBC driver and just update the tables direct).

NB - this direct access to the tables is very dangerous and a good way to destroy your database unless you know exactlywhat you are doing! (which of course as software engineers we all do....)