The RBENGINE76.CFG or RBENGINE90_64.CFG I was trying to stay generic and should have said ' RBENGINE##.CFG
I am still old school from back then. Sincerely, Paul D. From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, February 18, 2010 6:14 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Time Out Paul: Honestly, I NEVER use rbase.cfg files. Not since 6.5 days when it was required that you had one. Can't even tell you were the heck my rbase.cfg files are, now that my clients are (almost all) on version 7.X. My rbase.dat file (or whatever) always sets the database-wide settings. So everyone who comes in gets the same settings. I've never had an instance where a particular user required different settings. If they did, then I guess I'd put those settings in a lookup table or hard-code them or something.... Karen ime got out of format and all day was 'DataTime invalid, error 122's etc... ' I recall somebody once saying, 'it is ok to have a generic Rbase.cfg on the server that all users use.' I have separate cfgs for every workstation and somehow? Time input got switched to HHMM and not HH:MM:SS like on 8 stations. So I was just going to put a cfg file on the server. Is it safe? I am in a bind for time at the moment. I can see I am going to have to switch to Mike B.'s approach. But in the mean time any thoughts would be appreciated. Paul D.
