Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread |
Messages 1 to 4 of 4 total |
Access to the RemoteDatabase Directory |
Thu, Feb 16 2006 8:51 AM | Permanent Link |
Paul Baumann | Hello,
currently i am migrating a programm from local to remote. In every database directory there is a "db.ini" where i store defaults of the database. in stLocal mode it is no problem to acces the ini-file. in stRemote mode i have also to access this ini-file, but from every user machine i need a valid path information for the access. i already tried "AdminSession.GetRemoteDatabase(RemoteBase,DBDiscription,DBPath);" but this gives me only the path on server. Any idea to solve the problem, keeping in mind that access to server can be via Port, server runs as service and all that stuff. BTW: i am not very expericend about the remote stuff, so i perhabs missed something simple: Thank you PB |
Thu, Feb 16 2006 9:46 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Paul
The best suggestion is - don't use an ini file use a table - I keep very little information in an ini file generally. There are exceptions, but usually it is simply the location of the database, and that file is kept in the application's exe directory. I then have a two tier system - 1 table for application parameters and a second for users. Roy Lambert |
Thu, Feb 16 2006 4:31 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Paul,
<< Any idea to solve the problem, >> You can either go with Roy's suggestion or you could create a server-side procedure that can be called to return the .INI file from the database server to the client. You can see an example of transferring a text file like that here: http://www.elevatesoft.com/dbisam4d5_customizing_engine.htm -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Feb 16 2006 11:25 PM | Permanent Link |
"Ralf Bertoldi" | Paul Baumann wrote:
> BTW: i am not very expericend about the remote stuff, so i perhabs > missed something simple: Thank you I used a lot of .ini stuff before I changed to C/S.. Kepp in mind that accessing stuff from a DB Server like Roy suggested is a lot faster than using .ini files. Opening files, read and close takes a lot time... like .ini files do.. a lot overhead... I did following: Every setting that is important for a client to connect to a server like IP/PORT/database/etc. settings I stored clientside.. Even specific Hardware settings like screen resolution's are stored on client side.. not all resolutions in a network are the same.. (if you would store heigth/width of windows..) Every setting that is important for a client if it's connected... I store them in the database... Ralf Mimoun put a nice sample to the binaries how .ini values could be stored on serverside.... "DBISAM INIFile simulator"... it's a good point to start with... HIH ralf p.s. (native language.. my english is awful... Alles was nicht maschinenspezifisch, sprich Client spezifisch ist ruhig in der Datenbank speichern.. Geht es nur um die verfugbaren Datenbanken welche auf dem Server vorhanden sind,.. zentrale Tabelle auf dem Server anlegen, sonst die verfuegbaren Datenbanken vom Server auslesen. |
This web page was last updated on Saturday, May 4, 2024 at 12:54 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |