![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread |
Messages 1 to 4 of 4 total |
![]() |
Thu, Mar 1 2007 5:31 AM | Permanent Link |
"Petter Topp" | Hi!
We have a solution (Several applications) today that uses a Local connection to the Dbisam tables. Recently we have had some problems with tables being corrupt probably because a client computer terminates (E.g. Power failure). I have been considering using C/S for some time now, but fear that this will generate a whole lot of unforeseen work like login issues, administrating users, and so on. In this solution we already have a "server" application running (For custom communication with non Windows devices and windows CE devices). I would really like to hear your views (pros and cons) on using my existing server as a Dbisam Server (Implementing the DBServr source) or not. Regards Petter Topp D7 / BDS 2006 / Dbisam 4 |
Thu, Mar 1 2007 1:17 PM | Permanent Link |
"Jose Eduardo Helminsky" | Petter
The use of out-of-box DBISAM server or customize it is your choice. You can start using it and migrating some complex tasks with tables to server (remote procedures). It is very easy to change from local to remote connection and you can login using default user/password without having work to do and transparent to the users. The only thing you must do is create an alias to your database to point to a specific folder at server side to use with client applications. Just put the following code at beginning of your application (Datamodule create for example) just before open databases or tables with Session do begin RemoteUser := 'admin'; RemotePassword := 'DBAdmin'; SessionType := stRemote; SessionName := 'SS'; RemoteAddress := '192.168.0.1'; // the address you install the dbsrvr application RemotePort := 12005 RemotePingInterval := 30; RemotePing := True; LockProtocol := lpOptimistic; ForceBufferFlush := False; with Database do begin SessionName := 'SS'; DatabaseName := 'YourDBName'; RemoteDatabase := 'YourDBName'; Connected := True; end; // Just use your application in the same way you are using now. Eduardo |
Fri, Mar 2 2007 7:07 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Petter,
<< In this solution we already have a "server" application running (For custom communication with non Windows devices and windows CE devices). I would really like to hear your views (pros and cons) on using my existing server as a Dbisam Server (Implementing the DBServr source) or not. >> Sure, that will work fine. Just simply drop a TDBISAMEngine component on the main form of the existing server, set the EngineType to etServer, and that's all that is required for a basic setup. Of course, if you want to display connections, etc. in your server then you should look to the dbsrvr.drp source code on how to do so. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Mar 2 2007 11:23 AM | Permanent Link |
"Jose Eduardo Helminsky" | Tim
Reading slowly the main thread I have realized I gave the wrong answer to the question. Eduardo |
This web page was last updated on Wednesday, August 14, 2024 at 07:31 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |