Book a Demo

Author Topic: Problems with version control  (Read 3623 times)

rezaTech

  • EA User
  • **
  • Posts: 21
  • Karma: +0/-0
    • View Profile
Problems with version control
« on: November 08, 2008, 09:02:48 pm »
hi
I am trying to use Visual Source Safe for version controlling. After creating and putting my EA project into source safe, when i try to open the project from the client machine by "get latest", it gives me an error.

The error is---"The Microsoft Jet database engine cannot open the file 'D:\my EA project.EAP'. It is already opened exclusively by another user or you need permission to view its data."

But no one has opened the project and i have permission as well.
can anyone help me in this regard? pleaseeee

Takeshi K

  • EA User
  • **
  • Posts: 632
  • Karma: +43/-1
    • View Profile
    • Sparx Systems Japan
Re: Problems with version control
« Reply #1 on: November 10, 2008, 05:22:32 pm »
Maybe the EA project file is read-only. If so, you need to change it to writeable.

I think it is better not to put the EA project file itself but use EA's version control features.

Hope this helps,
--
t-kouno

Elham

  • EA User
  • **
  • Posts: 21
  • Karma: +0/-0
    • View Profile
Re: Problems with version control
« Reply #2 on: November 10, 2008, 06:33:49 pm »
Sorce safe make resources shared and control this sharing.Ea use Access database, and Access database file can't be shared.You can not use EA in Source safe
« Last Edit: November 10, 2008, 06:34:42 pm by Elham »

rezaTech

  • EA User
  • **
  • Posts: 21
  • Karma: +0/-0
    • View Profile
Re: Problems with version control
« Reply #3 on: November 11, 2008, 05:39:17 pm »
hi.
i managed to use Source Safe with my EA project. But there is one problem. I have few packages and each package contains multiple (10/12) use cases. Seems EA maintain control on packages. So if anyone checked out a package others cannot check that out.
In a single package i have multiple use case writers to write different use cases. With this type of package control multiple writers can not write use cases simulteneously under version control.
Can anyone help me with some good idea????