Dear dmcg,

Thank you for the insights. 

*Don’t think of jbase accounts as you would in other pick environments.*

 jBASE is my first MV database and I have read only jBASE documentation. So 
I don't have knowledge of accounts in other MV databases. I am wondering if 
I should use accounts at all.



On Friday, 9 September 2016 19:11:38 UTC+2, [email protected] wrote:
>
> Best practices are best defined based upon your particular needs.  The 
> first part (purely using examples) is to separate the environment from the 
> application(s)  For example, load the server with c:\jbase5\5………….
> Load the application(s) on 
> E:\jbase\.....................................................
> The libraries bin/lib might be loaded on either E:\jbase or C:\jbase5\ 
> such that you have 5.X, dev, etc.
> Having  the jbase environment on a separate drive makes OS or jBase 
> back-up more efficient.
> Don’t think of jbase accounts as you would in other pick environments.  
> There are other (better?) ways of dealing with user access and 
> application(s) access.  One of the best aspects of jBase is that it can be
> delt with from more of an OS perspective using native tools, etc.  Take 
> maximum advantage of that.
> Source libraries, for instance may be native directories such that native 
> OS tools may be used.  [When creating, create an ,OBJECT section.  This 
> allows the source to not be “contaminated” with object code to better
> manage the source.  It also allows the use of third party source/version 
> control systems (though many are a pain).  Again, depending upon the number 
> of programmers, applications, etc.  your needs SHOULD NOT be
> shoe-horned into someone else’s view of best practices.  Swatting nats 
> with sledge hammers works but ………………..
>
>  
>
> *From:* [email protected] <javascript:> [mailto:
> [email protected] <javascript:>] *On Behalf Of *Nagarjuna Siddam
> *Sent:* Friday, September 9, 2016 3:34 AM
> *To:* jBASE <[email protected] <javascript:>>
> *Subject:* Best practices for designing database
>
>  
>
> Hello Everyone,
>
> I am designing my first jBASE database. I am confused about how to 
> organize the database storage. (Where to put data files, where to put user 
> programs and libraries, how to structure accounts etc.,).
>
> Can someone with experience provide a list of best practices for jBASE 
> regarding above things.
>
> Thank you in advance.
>
> Regards
> Nagarjuna
>
> -- 
> -- 
> IMPORTANT: T24/Globus posts are no longer accepted on this forum.
>  
> To post, send email to [email protected] <javascript:>
> To unsubscribe, send email to [email protected] <javascript:>
> For more options, visit this group at 
> http://groups.google.com/group/jBASE?hl=en
>
> --- 
> You received this message because you are subscribed to the Google Groups 
> "jBASE" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
IMPORTANT: T24/Globus posts are no longer accepted on this forum.

To post, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"jBASE" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to