Dropping Open Workbench: Back to Microsoft Project

As much as I hate to admit it, I'm going back to Microsoft Project. I've worked for several weeks to get Open Workbench working the way I like. But there are two very important issues that I couldn't get to work in OW.

The first was I had to double-click each task and assign dependencies and resources through the dialog box. I hated that. In MS Project, all you do is type the name of the resource to assign it. To set a predecessor, you type in the number of the task. As for as I know, I couldn't do that in OW and it was the most frustrating thing about it.

Second, it is just not as user friendly as I would expect from a software program. I really tried to learn it and make it useful for me, but in the end I wasted a lot of time and effort working to make the projects work the way I liked. I guess you do get what you pay for... sometimes.

Honestly, I have to give Microsoft credit for their good usability and ease-of-use principles in their software. While a lot of people disdain them for various things (including myself), some things they do extremely well.

On a side note. I've never seen Microsoft as an INNOVATOR in technology. They've always been the COPY CATS with a good marketing plan. They copied Windows from Apple, copied Java with C#, began copying the iPhone with there phone (whatever the name was), copied Adobe Flex with Silverlight (??). Anyway, if there is one company that has a damn good marketing team, its Microsoft. If there is a company that has damn good innovations, it certainly isn't them.

In my opinion... Of course...

Installing Open Workbench

Open Workbench is an open source project scheduling tool for Windows. Due to personal and corporate budget constraints, I've quickly found interest in this tool. Also, trying it out seemed interesting due to the fact that it calculates work and scheduling events more intuitively than Microsoft Project.

However, I've had some difficulty in installing Open Workbench and allowing it to run properly on my machine. It looks as if the program does not use proper security access for Windows. I always work in a limited user account in Windows and only run in Admin for rare administrative tasks (like installing programs). Well, after installing Open Workbench via an Admin user, it wouldn't run. I could have setup the program to "Run with different credentials" in Windows, but, I'd rather not require all users to enter the admin password.

Installing it strictly as a limited user didn't work because the installer couldn't write to C:\Program Files.

Allowing the limited user Full Control over the entire C:\Program Files directory was out of the question.

SOLUTION: Now, I know enough about Windows security to mess up a machine. But, I'm nowhere near an expert. So, I made a simple work around that I believe is more secure. As an Admin user, I created a folder C:\Program Files\Open Workbench and gave the Users group Full Control over that directory only. Then I installed Open Workbench from the limited user account into its default directory (C:\Program Files\Open Workbench). Since the folder already existed and it had full access, the install worked. The program now runs properly as either an admin or limited user.

However, I've only installed the darn thing. I haven't run it and thus, we'll have to see if the program runs properly down the road.

Contact Chris SchofieldBlogCFC was created by Raymond Camden. This blog is running version 5.9.001.