Book a Demo

Author Topic: General Types - Requirements  (Read 4802 times)

slbrook

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
  • Today is a gift. Have fun!
    • View Profile
General Types - Requirements
« on: September 21, 2007, 07:24:52 am »
I would like to add "Non-Functional" as General Types /Requirements, but Non-Functional does not fit with the field length.
I suggest that the field length be increased to accommodate this. I am using Build 816.
Thank you,
Scott Brookhart

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: General Types - Requirements
« Reply #1 on: September 22, 2007, 10:47:07 am »
Good idea.

I wonder if this somehow got tweaked in the change to version 7.0. Seems someone should have noticed this before now.

David
No, you can't have it!

dbax

  • EA User
  • **
  • Posts: 69
  • Karma: +0/-0
  • One EA To Rule Them All
    • View Profile
Re: General Types - Requirements
« Reply #2 on: September 22, 2007, 07:29:54 pm »
I have checked it in version 7.0 and there's still a 12 character limit on this field.
However, in the meantime you could do it yourself. All you have to do is change it to be larger and to do that you have to change the length of the Requirement field in table "t_requiretypes". If you have an eap project file (local project file) then you need to open it in MS Access (simple Open With would work), version 97 unfortunately and perform the change. If you have higher version of MS Access then you need to up-convert to at least version 2000 and then back to version 97 (Caution: This will not work with Access 2007). Alternatively, if you have your project in DBMS repository, like SQL Server then you need to do the same but through that DBMS tool or simple ALTER TABLE statement.
I've just tried it and it worked.

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: General Types - Requirements
« Reply #3 on: September 23, 2007, 09:45:17 am »
Yes, that will definitely work.

Still, you'd need to do that for every project. And, if an update from Sparx contained the EABase project you could overwrite your default changes.

Ideally this should be remedied by Sparx.
No, you can't have it!