When I worked with ms-access, I was thought it’s a good idea to have one data file and one app file (and link from the app file to the tables in the data file).
How do I do it in Base?
Should I change my way of thinking?
thanks
Hello,
Base does not have that capability yet. If memory is correct, there is an outstanding request for this. You can access multiple data sources using switchboard (or standalone forms). See this post → [Tutorial] Standalone Forms / Switchboard. But this is not the same as what Access allows. Macro coding is needed to be even remotely similar.
You can also code macros to access data from another .odb or database but there is a good deal of effort required there also.
Edit:
If you are using Base with the default HSQLDB embedded, it is recommended to move to either a split DB or external DB such as MySQL or PostgreSQL or others. This is a very old version. The embedded DB can have problems with losing data when used with large amounts of data or embedded graphics such as pictures. There is an on-going project to replace the default DB with Firebird embedded DB. With these external DB’s you do have separation of data from the application.
If this answers your question please tick the 
(upper left area of answer). It helps others to know there was an accepted answer.
I find it somewhat disturbing
If you use a BIG app, yes- it makes sense to install My-SQL or so and make the connectios
But for a small app (clients names, personal data, contact info) what you are really telling me that Base today is not a good solution.
or did I get you wrong?
Base is a good solution. What is being said is the the default HSQLDB which ships with LO is old and prone to problems depending upon data. This is due to its being enveloped & expanded in the .odb - a problem of the DB and not of Base itself. This is why the current project of replacing with Firebird is proceeding.
Using a Split DB (HSQL outside of the .odb) will not only remedy the problem but actually allow a newer version of HSQL to be used which in turn has more capabilities…
You can easily start using split DB’s. See the document in my answer on this post → Split DB setup instructions. It contains links to original instructions and alternative methods to converting existing embedded Tables etc.
BTW, my main database is MySQL. I use it on a daily basis and the main application only has a few thousand records. I also occasionally use PostgreSQL and some SQLite for testing. Of split databases I have many - mainly for testing. SQL in the HSQL embedded is very restrictive and the split DB’s overcome this with a newer HSQL. Embedded is still used for quick testing and posting of solutions on the forum.