Eleven Tips for Moving to OpenOffice.org

Replacing a complicated piece of software like an office suite can be a major undertaking. But, if you apply a few simple rules to make sure your needs are met, you'll be ready to be productive on the new software right away.
______________________

-- Bruce Byfield (nanday)

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Largest Single Impediment

Arthur Fuller's picture

From what I have seen, the largest single impediment to persuading my clients (and myself) to making the move is the absence of VBA or some equivalent language. On the Windows platform I have invested years of programming to achieve Offic Automation, combining Word, Excel, Access and SQL Server to deliver integrated apps that work brilliantly.

I would love to port these apps to OOo but as far as I can see, there is no available path to get from here to there.

I'm talking about LOTS of VBA code. 50K lines per application, at a casual guess. Simple formula-translations are just that, simple, but complex code is difficult if not impossible.

Lots of my clients would love to make the move, but until I can provide a conversion path, then it's a non-starter. And by this I don't just mean that OOo can read an Excel or Word file and save it natively -- I mean that the VBA part is the most important, and without that we have a non-starter.

Arthur

Geek Guide
The DevOps Toolbox

Tools and Technologies for Scale and Reliability
by Linux Journal Editor Bill Childers

Get your free copy today

Sponsored by IBM

Upcoming Webinar
8 Signs You're Beyond Cron

Scheduling Crontabs With an Enterprise Scheduler
11am CDT, April 29th
Moderated by Linux Journal Contributor Mike Diehl

Sign up now

Sponsored by Skybot