Thanks Will.
That is more or less what i was talking about when I talked about "splitting" a
Microsoft Access database so the data was on one computer (the server) and the
user interface with the Microsoft Jet database engine, custom queries, data
entry forms, reports, etc was on another.
Just to chime in on the terminology...
In my current job I do back-end development for an NGO. We have another
developer who works on the front end and a couple people working on a mobile
app.
The back end is an application that runs on an Amazon Web Service instance. The
front end is a web
Thanks Jim. Regarding Front End and Back End...
When I used to develop Microsoft Access databases I would split it such
that...- All the data was stored on a local peer-to-peer server. We called that
the "Back End"
- The "Front End" would have the user interface with the queries, data entry
On 2020-10-25 08:29, Fran_3 via gnucash-user wrote:
- I have always considered GnuCash as a program that must be installed on the
local machine.
- With the myBiz.gnucash file also on the local machine.
- This means that two users can not open GnuCash on their respective machines
and access
- I have always considered GnuCash as a program that must be installed on the
local machine.
- With the myBiz.gnucash file also on the local machine.
- This means that two users can not open GnuCash on their respective machines
and access the myBiz.gnucash data file at the same time...
1 - Right
