They are rolling out Business Objects where I work. In my gut, I think MS
Access iis probably better.
Does anyone here know the differences (performance-wise) between the two?
If "Busines Objects" means some 3rd party software, then you will have a
learning curve
If "Busines Objects" means some programmer at your office developed a class
library, then it will also have a learning curve, but it will let you change
your code so that it's tighter. Imagine the Northwind database, how cool it
could become, if it had programming that thinks in terms of customer
collection of customer objects that had methods, instead of having to
manipulate recordsets.
While performance is important, you also have to think about how
maintainable the code is. If your application can operate on a high level
of abstraction, then GREAT! If your application is "married" to the nuts
and bolts of the physical storage, then people like me will be sending
proposals for incredible amounts of money to fix it.
Here are some references:
What to do:
http://www.amazon.com/gp/product/02...102-0597696-8121709?s=books&v=glance&n=283155
(Or if that has "session junk" in it, then just goto Amazon and do a search
on "Design Patterns" and look at the first book on the list. It should be
white with a blue border)
What NOT to EVER DO:
Anything on this guy's web site should be absolutely forbidden:
http://mindprod.com/jgloss/unmain.html
--
Peace & happy computing,
Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSensei