|
| Development with Local Server and install HFSQL Client Server |
| Iniciado por gallen.dbmc, 01,feb. 2017 23:01 - 1 respuesta |
| |
| | | |
|
| |
Miembro registrado
31 mensajes |
|
| Publicado el 01,febrero 2017 - 23:01 |
When I am developing an application I usually use HFSQL Classic but with my current project the end product will be HFSQL Client/Server.
What is the recommended approach for handling this? I have been thinking of using an INI file to store the connection parameters.
And perhaps a stupid (beginner) question: will the EXE get installed and run from the server machine or get installed on all of the work stations?
Thanks,
Garry |
| |
| |
| | | |
|
| | |
| |
| Publicado el 02,febrero 2017 - 14:13 |
Hi Garry,
Le 2/1/2017 à 5:01 PM, Garry a écrit :
When I am developing an application I usually use HFSQL Classic but with
my current project the end product will be HFSQL Client/Server.
What is the recommended approach for handling this? I have been thinking
of using an INI file to store the connection parameters.
That's the usual way of doing this. Analysis in classic, and a
hchangeconnexion..
And perhaps a stupid (beginner) question: will the EXE get installed and
run from the server machine or get installed on all of the work stations?
Both are possible. it's really up to you. With the server install, there
is only one uodate to do, but everybody must be out of the program at
the same time...
Juts in case, there is a fully fonctionning code available in WXEDM on
my web site (including a wiezard asking the questions and writing in the
ini file)
Best regards
--
Fabrice Harari
International WinDev, WebDev and WinDev mobile Consulting
Ready for you: WXShowroom.com, WXReplication (open source) and now WXEDM
(open source)
More information on http://www.fabriceharari.com
Thanks,
Garry |
| |
| |
| | | |
|
| | | | |
| | |
|