Connecting Livecode app to a database on a local network...
Posted: Mon Apr 23, 2012 12:45 am
Hi,
These questions are coming from a zero-experience perspective, having just loaded Livecode and never programmed in my life... I briefly worked on a Filemaker 7 database years ago.
Could some folks help me understand how Livecode works with a database on a local network. What I would like to do is create a livecode application that I can install on every PC on a windows workgroup (approx. 5 workstations), and have them all access the same database records.
For this do I have to create a server-version of the application, which kind of talks to the database, and then create a client-version for all the other workstations? Or do I just install a database on any one of the workstations and then 'point' all of the installed standalone Livecode applications to that single database... and would having an actual Windows server as opposed to a Windows workgroup offer any advantages related to Livecode development? I'm not sure how data integrity is controlled and how people are not allowed to write things concurrently. Perhaps these kinds of features are native to most database engines?
Also, when you deploy the final installable application, would the database have to be installed totally separately or does the installer for your final Livecode app also have the ability to coordinate the installation of a 3rd party database... that would be pretty nice. If this is the case would I make a server-version of the application which installs the client-app and ALSO installs the database, and a client-version of the application that ONLY installs the application, which would be used on any incoming new workstations. (Same application, essentially, just a different installer).
Still a lot of learning curve ahead of me.
But thanks in advance for any help getting on board!
These questions are coming from a zero-experience perspective, having just loaded Livecode and never programmed in my life... I briefly worked on a Filemaker 7 database years ago.
Could some folks help me understand how Livecode works with a database on a local network. What I would like to do is create a livecode application that I can install on every PC on a windows workgroup (approx. 5 workstations), and have them all access the same database records.
For this do I have to create a server-version of the application, which kind of talks to the database, and then create a client-version for all the other workstations? Or do I just install a database on any one of the workstations and then 'point' all of the installed standalone Livecode applications to that single database... and would having an actual Windows server as opposed to a Windows workgroup offer any advantages related to Livecode development? I'm not sure how data integrity is controlled and how people are not allowed to write things concurrently. Perhaps these kinds of features are native to most database engines?
Also, when you deploy the final installable application, would the database have to be installed totally separately or does the installer for your final Livecode app also have the ability to coordinate the installation of a 3rd party database... that would be pretty nice. If this is the case would I make a server-version of the application which installs the client-app and ALSO installs the database, and a client-version of the application that ONLY installs the application, which would be used on any incoming new workstations. (Same application, essentially, just a different installer).
Still a lot of learning curve ahead of me.
But thanks in advance for any help getting on board!