- #Openoffice basic macros how to
- #Openoffice basic macros software
- #Openoffice basic macros code
- #Openoffice basic macros free
#Openoffice basic macros code
I’m not saying that there never are occations where a pure Access/OOo Base solution is the right thing to do, just that they rarely are.While much of the underlying logic behind OpenOffice Basic compares to that of Visual Basic for Applications, there exists fundamental differences to the way the code is constructed. But on the other hand you are not worse off, than if you had developed all of the functionality in Access or OOo Base. The downside of this way of development is that stored procedures and triggers are database vender specific, so it will be hard for you to change database vender. If you don’t like java for GUI build it in Access or OOo Base. There are plenty of java IDEs that make the job of building a GUI and connect it to the business logic in the database very simple. As database you could use Postgresql, Firebird or even MS-SQL server if Microsoft are your heros. However using plain old java for GUI and a relational database and stored procedure for data storage and business logic creates very fast and reliable solutions. I agree with you that J2EE is overly complex in most situations, if you considered using MS-Access you almost certainly are in that kind of situation. It usually assumes that the developer should do things in the surrounding php code that normally are handled automagically by the database (even MS Access is better in this respect).
#Openoffice basic macros how to
referential integrity is not turned on by default.Īnd most people doesn’t know how to turn it on. Even in late versions like 5.0, things most people take for granted e.g. Even though MySQL is a server oriented system, it is not exactly a good database. In this case replacing one bad database for an even worse will not help much. That’s true, but if you use a bad tool chances are that the outcome will be worse than what it could have been, at any given quality of your developers. *JUST* because you use a good tool, the result does not need to be good also. I have also seen some people porting over Access apps to LAMP with a catastrophic mess in MySQL and PHP. So the addition of Java code in Base won’t matter. But it gives the advantage of one code base for all platforms, which is great. And OO.o is already big and a memory eater, even though most of the code base is C++, because it basically creates it’s own runtime library, which is expensive on resources. Again, Java the base language has some good features. The fact that it partially uses Java is okay. When it reaches maturity, however, it might be pretty slick and will fullfil a need for replacing MS Office completely.
#Openoffice basic macros software
Base is a brand spakin’ new software product, and is going to have it’s problems. But J2SE (standard) development isn’t so over complex, and pretty productive (so long as Swing isn’t used too heavily).Īnyway, this thread is about OO.o Base. Java the base language has it’s strengths, and J2EE has incredible capabilities, but handles those capabilities in the most complex ways possible. Whew.Īctually it’s a fairly common thing for large J2EE projects to go down the drain, because the complexity overwhelms the devs, architects, and project managers. J2EE is extremely, extremely complex … it’s just a labyrinth of complexity, and requires the highest order of programming skill and experience, knowledge of the massive and numberous APIs, knowledge of the gazillion frameworks, and frameworks that are wrappers of other frameworks, and the subtleties of putting all of the that together, and the subtleties of 100% OOP.
“Some months ago, I saw a J2EE project gone completely down the drain – because it has gone too complex and the developers had too few expirience … now what was the problem ? J2EE or the developers ? I thing you can answer this question yourself …”
#Openoffice basic macros free
On topic, kind of I’d love to see Apple drop Apple Works, port OpenOffice to MacOS X natively and of course make it HIG compliant, then re-badge their version as AppleWorks X or something that is buzz word compliant they would get a damn good office suite that is comparable to Office, and will be able to bundle it free of charge with their desktop systems. Agreed those who use the really advanced features are the IS staff the ones who setup internal databases, and even they’re moveing to opensource solutions like Firebird, MySQL and Postgres – its not about features necesssarily, its GET – Good Enough Technology – it may not be sexy or technologically the best, but it still does a pretty damn good job, but without the massive costs.Īs for end users, I agree most would probably use less than 20% of the features the end users the article was talking about sounded more like the wizard using variety where a set of step by step screens help them setup a database – everything automated.
0 kommentar(er)
