Skip to main content
March 24, 2009
Question

Problems opening a project from RoboSource Control for the first time

  • March 24, 2009
  • 2 replies
  • 1741 views
I am trying to set up myself and one other user with a RH Project File in RoboSource Control. I've been following Matthew Ellison's article, "Getting started with RoboSource Control 3" and have gotten stuck at the point of "Opening a project from version control for the first time."

I successfully added the project file to the source control db as "admin" and thus, a connection was made for me in that process. Therefore, I have a local copy of the RoboSource Control project file that I can access just fine.

The problem is that we are unable to get a local copy of the RoboSource Control project file saved to my co-worker's PC, nor can I create a 2nd local copy for myself on my own PC with a different login than "admin". (I've added both co-worker and myself as user accounts, in addition to "admin".) In both cases the Open Project dialog box gets hung up for a long time, only to eventually display an error message saying that the "default.cpd is corrupt and can't be opened. Try deleting this file and reopening the .xpj." I then click OK and get an empty RH viewer. I deleted the "default.cpd" and tried reopening the .xpj but go the same error message.

Any troubleshooting ideas? I will gladly provide more specifics.

Thanks,
Beth
This topic has been closed for replies.

2 replies

Gravenstein
Inspiring
April 8, 2009

Is this a project that was upgraded from X5, by any chance? Check for a zero-size rhvariable.apj file in your root directory. If you have one of those, then that's your culprit. See Peter Grainge's snippet 79 for more info.

HTH

G.

Captiv8r
Legend
March 24, 2009
Hi Beth

This is my own opinion of course, but in my own view, unless you have perhaps four or more authors in the mix I find Source Control to be unnecessary overkill. Sort of like shooting a fly with a bazooka.

If it's just you and one other author, you may be better off avoiding the Source Control headaches and simply manage the project between the two of you using simple communication.

Keep in mind that Source Control is going to add another layer of complexity to your actions. And another layer means another area for things to go wrong.

Cheers... Rick
March 24, 2009
Hi Rick,
Do you mean simple communication like walking over to my co-worker's desk and talking to her?? What a concept!

After spending the better part of 2 days working on this, I am considering abandoning the project -- but then I have the strong desire to figure this dang thing out, too!

Is RoboSource a good solution when there are 4 or more users, or is the app problematic in general?

Thanks,
Beth
RoboWizard
Inspiring
March 24, 2009
Hi Beth

Actually, I offer a free eBook that describes a method that would work for that. Click here to visit the site to download the eBook. So rather than explain how it can all be done, you may download the eBook if you like.

I don't know that RoboSource Control is any buggier than any other Source Control system. Heck, it's software after all. And I've never met a piece of software yet that didn't have a wart or wrinkle here and there.

Indeed, when you have many users involved Source Control can be very helpful as it helps prevent everyone from stepping on one another's toes. Oops, I just saved my Word document and overwrote Sally's, effectively undoing all Sally had done this morning! Things such as that.

In my viewpoint Source control is pretty straightforward until you begin tackling the following things:

* A folder or topic file name is changed. Hmmm, how is everyone else notified? What happens?
* A folder or topic file is added. Again, same ponderings as above.
* How to handle simultaneous updates to the TOC/Index/Glossary. Theoretically only a single person may modify these elements at a time. I'm not sure how that works in an integrated RoboSource Control system.

Cheers... Rick