I have been running with option 1 for years. The compiled app is only 6 megs so it loads in less than a blink of an eye over our gigabit network. If you are not running gigabit I would do it. it is very cheap nowadays to do. Rbase fly's over gigabit.
I have never seen any message about the exe being safe. If you Google it, it will tell you how to turn off the message if you get it. If you go with option 2 you will need to copy that app to each machine every time you update it. Dan Goldberg From: jan johansen Sent: Thursday, September 20, 2012 2:43 PM To: RBASE-L Mailing List 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
