It would really help my learning to know what type of object the results from a query run from a macro would be. I’ve been using it for years, following the code I’ve seen others using. But I’ve never really understood or known the object type so I could research the options…
Also, is there a specific object type for SQL statements?
@Villeroy Thanks! Unfortunately, even though I know I’ve used MRI in the past, I don’t remember a whole lot about it, but I know I had it installed and working, and it was a ton of help. Now, in LO 7, I don’t see any Add-ons in the Tools menu.
MRI adds the menu entries when you install it. I use MRI 1.3.4 with LO 6 and 7.
By the way: What are you trying to do actually? What is it that requires any macro coding?
@Villeroy Thanks for taking the time to help! I don’t see 1.3.4 on the openoffice extensions page you linked in your tutorial. https://extensions.openoffice.org/en/project/MRI only goes to 1.3.3.
What are you trying to do actually? What is it that requires any macro coding?
Make myself crazy. Actually, I’m trying to enforce compliance with our accredited lab’s Quality Management System and make data entry slicker.
Did you restart the office suite? Did you mind the nasty “quick-starter” when restarting the office suite?
Do you see a Basic library “MriLib”?
Does the following Basic work?
srv = createUnoService( "mytools.Mri" )
srv.inspect(StarDesktop)Forget it or use a slicker database frontend. I avoid macros like Covid although I’m able to write them. Design a set of slick input forms and you won’t need any silly Basic code.
We really can’t. We’re kind of married to what we have. What’s the point of macros being available if the answer is going to be “Avoid using that tool”? My suspicion is that you’re avoiding telling me I’m not smart enough to use it… The reality is that may be true. I started using it before I had to have a baseball-sized tumor removed from my brain.
I don’t see your database. If it happens to be a properly normalized relational database, you can build very well usable forms with no code and finally add some supporting macro code. Base forms support one-to-many, one-to-one and many-to-many relations in arbitrary depth. With some knowledge on parameter queries you get much better results within hours than with macro code in weeks.
I’m not educated enough to know what that means.
Are you talking about machine run time or the time I spend getting the whole system to do what I need. My main problem is that most of my understanding comes from the schools of hard knocks or trial-and-error or internet searches.
Even an experienced professional takes some weeks to get his/her head around this monster API whereas the fundamentals of SQL language are the same since the 70ies. Trial-and-error is the best way to fail when dealing with formal languages.
Most database related trouble comes from a lack of theoretical knowledge on a basic level such as database normalization.
The best source of Base related information is forum.openoffice.org with its Base forum and a section with Base tutorials together with the LibreOffice Base guide English documentation | LibreOffice Documentation - Your documentation for LibreOffice.