Marco, The mechanics of a database running on the same local drives (ie: the server) is the same whether it's Sql Server or RBase, since the recordsets never leave the physical server environment.
When it comes to the DBMS, then you are talking apples and oranges. Sql Server requires a different toolset to manage and not because I'm biased in any way, but RBase wins that contest hands down. ----- Original Message ----- From: "Marco Groeneveld" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Friday, September 21, 2012 2:16 AM Subject: [RBASE-L] - Re: compiled app Hi, I was at a company using only thin clients connected to a desktop server. I was surprised to see how easy and fast the concept was. Even the local printer was always available on any place. In this way there is no need for web access. I have seen also some trouble with connection error, browser updates, etc. Is there experience which Remote software is the best to work with R:BASE on server and on client (Windows / IOS). I am only not sure if in this concept it is wise to use the R:BASE database or SQL Server is a better choice for faster access on a network. Regards, Marco ----- Original Message ----- From: Paul Buckley To: RBASE-L Mailing List Sent: Friday, September 21, 2012 12:31 AM Subject: [RBASE-L] - Re: compiled app Jan, I have become a HUGE fan of running using Terminal Services and logging with Remote Access. You get the best of both worlds, only 1 copy of the EXE to update and nothing running across the network, it all runs on the server. Licenses are cheap too. There can be some challenges setting up printers but I can probably help you with that. That's my 2 cents worth. Paul From: [email protected] [mailto:[email protected]] On Behalf Of jan johansen Sent: Thursday, September 20, 2012 6:18 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: compiled app Tom, Thank you. That get's rid of the message. No have to figure out why it takes 10 seconds to start. Some network security issue somewhere I guess. -----Original Message----- From: TOM HART <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Thu, 20 Sep 2012 15:05:54 -0700 (PDT) Subject: [RBASE-L] - Re: compiled app On you con The app has to be pulled across the network each time and answer the question "is this exe safe?" have you tried under internet options>security>local intranet>advanced set file://'yourservername' that will get ride of the message. Tom Hart ---------------------------------------------------------------------------- From: jan johansen <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Thu, September 20, 2012 4:44:35 PM Subject: [RBASE-L] - compiled app Looking for some feedback. I have been using the compiler for years but am looking at my configuration. There are 2 basic ways to use this on a server. 1. Compile the app to an EXE an place it on a server Pros Ease of maintenance and distribution Pathing is easy (put a shortcut on a machine with the "start in" for the server which allows easy access to subfolders) Cons The app has to be pulled across the network each time and answer the question "is this exe safe?" 2. Compile the app and place it on each machine Pros App on machine. Only data is transfered (especially if you put your forms in the EXE) No security question Cons Pathing to subfolders of database is more difficult I would really like suggestions on solving the con of option 2. TIA Jan
