At 06:24 PM 12/14/2015, Tom Frederick wrote:
We have several questions related to our compiled database (RBaseX
Enterprise).
RbaseX.dat is the file used to build ElmCityDatabase.exe. The Rbase engine is
embedded along with one theme (Longhorn) used for messages.
RBengine.cfg is on
the server where the exe is located. The current config file has an
item called
Name:USER 20151129130838. How is this user ID used? If four users get on our
system through the exe on the server, they would all use that config
file which
has that USER ID. Does this user ID apply the same to all of the
users so that
user ID is used four times? Or are each user tracked through other means like
the User Privileges section? I have not used the Privileges at all, which can
explain some problems we have had with unannounced shutdowns. The database is
simply great in single user. In multi it works well, but I keep
finding little
tweaks I missed. This is just the next item that has come up. Thanks.
Tom,
Have you looked at the recent R:BASE X Enterprise Compiled applications made
available lately at http://www.razzak.com/sampleapplications/
Installing and deploying those applications on your server and running 'em in
a multi-user environment should provide you with a good model. You will notice
that everything is configured in one folder and all required files, including
the RBENGINEXE.CFG and RBENGINEXE.DLL, are also kept outside in the
same folder.
Embedding RBENGINEXE.DLL can create a MAJOR security headache when running
your compiled applications with embedded engine. Running the engine file in
Windows memory may not be an ideal configuration with all Windows Security,
etc.
Here is the explanation regarding the USER name in the RBENGINEXE.CFG file ...
When R:BASE or your Compiled R:BASE EXE is started, if there is no
configuration
file found in the path or in the same folder, R:BASE will create one with a
default USER name that is the text format of YYYYMMDDHHMMSS.
Your application login and user information should NEVER be dependent on the
USER name in the R:BASE configuration file, as this will be the same for every
user. You should consider using the unique logged-in user (CVAL('NetUser'))
to validate the actual logged-in user, etc. There are additional swift methods
to validate users and provide them with appropriate access to your application
menus, functions, etc.
You may also need to verify the SCRATCH setting folder with full access rights.
Hope that provides you with some blues's clues ...
Fell free to reach out to me with any questions.
Very Best R:egards,
Razzak
