I appear to have an ongoing issue with one particular (Flare 7.2) project wrt checking in changes to TFS.
When I want to check my files in the majority of files generate a 'conflicting changes' error message informing me that a newer version exists on the server. This I know not to be the case as I am the sole author working on the project.
Is this a known issue in Flare or TFS?
Any ideas on how best to resolve this or a suitable workaround?
Thanks - Ian
A newer version exists on the server!
Re: A newer version exists on the server!
This may be of no use to you, but since no-one else more knowledgable has replied yet, it just may help.
I've had an interesting few days as a Flare newbie trying to set up Perforce source control to work with Flare. One of the things that I found was that Flare and Perforce often get out of sync. Sometimes it is because someone else has checked in changes to a file in another workspace, but sometimes it is just Flare having a funny five minutes. If anything like that happens (for example, Flare thinks the file is checked out, so only offers me the Check In option, but the file is actually not checked out), try Source Control > Refresh. This will refresh Flare's view of the file, so it reports the file as being in the same state as your source control system thinks it is in. This is usually all it takes to get Flare to behave as expected. In fact, I now do this before doing any source control operation in Flare.
This may help you too. Source Control > Refresh is your friend!
I've had an interesting few days as a Flare newbie trying to set up Perforce source control to work with Flare. One of the things that I found was that Flare and Perforce often get out of sync. Sometimes it is because someone else has checked in changes to a file in another workspace, but sometimes it is just Flare having a funny five minutes. If anything like that happens (for example, Flare thinks the file is checked out, so only offers me the Check In option, but the file is actually not checked out), try Source Control > Refresh. This will refresh Flare's view of the file, so it reports the file as being in the same state as your source control system thinks it is in. This is usually all it takes to get Flare to behave as expected. In fact, I now do this before doing any source control operation in Flare.
This may help you too. Source Control > Refresh is your friend!
Marjorie
My goal in life is to be as good a person as my dogs already think I am.
My goal in life is to be as good a person as my dogs already think I am.
-
BaritoneJP
- Propeller Head
- Posts: 49
- Joined: Mon Jun 02, 2008 9:12 am
- Contact:
Re: A newer version exists on the server!
Has anyone had this issue ... and maybe a workaround ... hint ... explanation of what is going on?
I'm using Flare 8.1.2 and VSS
I have been using the Source Control > Refresh and is works ... but not all the time.
Allow multiple checkouts is NOT allowed on my VSS
Thank you for any assistance.
I'm using Flare 8.1.2 and VSS
I have been using the Source Control > Refresh and is works ... but not all the time.
Allow multiple checkouts is NOT allowed on my VSS
Thank you for any assistance.
Thank you for your comments and help with my quandary ...
Jamey
Jamey
-
BaritoneJP
- Propeller Head
- Posts: 49
- Joined: Mon Jun 02, 2008 9:12 am
- Contact:
Re: A newer version exists on the server!
OK ... now I have to use the Source Control > Refresh trick/method before I can Get latest Version All. If I don't refresh then Flare tells me everything is up-to-date. If I refresh first, then get all versions, I get this long list of retrieving files.
Has anyone seen this? Does anyone know what is going on? (I'm using VSS)
Does anyone have any "best practices" with VSS server settings?
Help please ...
Has anyone seen this? Does anyone know what is going on? (I'm using VSS)
Does anyone have any "best practices" with VSS server settings?
Help please ...
Thank you for your comments and help with my quandary ...
Jamey
Jamey