• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 289
  • Last Modified:

Visual Objects Programming Language

The company that I work for is considering a sales accounting package that is written in the “Visual Object” programming language.

Since the software package is very expensive I’d like to know if this is a widely used programming language and if not, why?  Are there any known problems etc.

Thanks, Sandra
2 Solutions
Mike TomlinsonMiddle School Assistant TeacherCommented:
(I haven't used this product myself...)

Look here on Experts-Exchange...there is no section devoted to "Visual Objects"...does that tell you anything?  =)
The fact that the most recent release of Visual Objects was over 2 years ago (Feb of 2004) should tell ou something.  And the fact that it is provided by Computer Associates tells me that this is a product the I would personally avoid like the plague.  I used to work for Computer Asscociates (actually for one of the many companies that they have absorbed over the years), and CA is not a nice company to have any dealings with.

The fact that CA has essentially decided to get out of the Application Tools market (and to support Unicenter almost exclusively, along with their Main Frame product base) should also tell you something about their long term commitment to products such as Visual Objects.  I strongly suspect that VO has a VERY VERY small customer base, and the likelihood of finding assistance with any questions or problems that you might encounter would be very small.

As Idle Mind points out, there is no EE Technical Support area for Visual Objects, which suggests that very few (if any) of the EE users are asking about VO.

Visual Objects used to be known as Clipper (in DOS days), which was arguably the best way to turn dBase code into a compiled application (best as in lesser chances of corrupt tables, and in terms of memory footprint too).  Clipper was great in its' day, I used to use it a lot - didn't like the inconsistent variable scoping on it though.  It supported any table structure where an "engine" was available for it, so it could cope (at that time) with dBase NDX indexes, Clipper NTX indexes, FoxPro CDX, and Dbase MDX.

VO was supposedly the Object Oriented path for Clipper, I went to a few technical seminars to try and summon up some enthusiasm to use it, but eventually chose to go a more conventional RAD route.  From recollection it tried to be back compatible with Clipper and the implementation therefore was a bit clunky.  I don't know whether they have moved away from the dBase family structure, or whether they have added other database "engines".

I do remember an Accounts package that was written using Clipper/VO, the perceived advantages at that time were that it was easily amendable by programmers conversant with Clipper, so that you could tailor it for different types of business, and that you only needed to buy the modules of interest to you.  But those selling points are not really relevant these days.

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now