Somewhere in this "SET EOF OFF" solution may exist an answer for one of my
problems.

Using 4.5++, the original set up was a single person operation.  I don't
believe that we had these problems back then.  Recently a server was
installed and others are now accessing RBase from the server. The only thing
I did was "set multi on" and no granting of rights is necessary (everyone
has all rights).  I simply placed an icon on each screen and all RBase
operations were on the server. The same RBASE.CFG is used by all. The
operating system is XP.

The problems do not seem to happen predictably.  There is no actual login
and a screen notice is presented "The SERVER.SYS file shows the user name
[EPU1]as already active." when a second user in on the system.  We always
hit <ENTER> to continue.

Problems:  

1)  If a client machine, with RBase active, remains out of use for more than
a minute or two the system kicks the user off on a single key stroke (screen
goes blue and to R> prompt). Sometimes a complete reset of all systems seems
to resolve issues. The actual time here may be moot since the trigger may be
caused by activity on the other machines.  I wonder if this is a SERVER.SYS
situation.

2) When printing an invoice, or when doing a look up, occasionally the
client machine seems to hang up and the operation is so incredibly slow.
Can this be a SET EOF OFF remedy?  We have been watching the task manager to
see if something is clogging the system but do not see a pattern yet.

So far, the program has been tested on two other single user systems and
neither problem has ever showed up. 

Thoughts appreciated

Steve Ambrosini


-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Dennis
McGrath
Sent: Monday, May 14, 2007 4:22 PM
To: RBASE-L Mailing List
Subject: [Spam]: [RBASE-L] - Re: Weird DOS behavior


I forced EOF ON at the top of the code file, just in case it was being
left off by some other code.

That fixed the problem.

Apparently, when EOF is OFF, the APPEND option strips off one too may
characters before writing the new data.  It makes sense because EOF OFF
causes fewer characters to be written to the end of the file when you
OUTPUT SCREEN.


Here is some code that writes a file correctly using APPEND
It uses a nifty trick to drop the EOF after the file is created.

SET EOF ON

out c:\test.txt
write 'Line1'
out scr

out c:\test.txt append
write 'Line2'
out scr

out c:\test.txt append
write 'Line3'
out scr

-- get rid of EOF after-the-fact
SET EOF OFF
out c:\test.txt append
out scr

SET EOF ON
RETURN

Dennis McGrath



-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Ron Rose
Sent: Monday, May 14, 2007 9:59 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Weird DOS behavior

Sugestions:
        OUTPUT filespec APPEND
         WRITE 'message', .var = w

SET VAR the " 'message', .var" to a varfirst, then WRITE .varfirst
Make it do a miltiple operation first, then the WRITE with a Single
operation.

RRR

----- Original Message -----
From: "Dennis McGrath" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Monday, May 14, 2007 6:59 AM
Subject: [RBASE-L] - Weird DOS behavior


> Has anyone seen this one?
>
>
>
> I'm running the latest build of RBDOS 7.5 but this has been a problem
> before that version.
>
>
>
> I have some logging code that appends data to a log file.
>
> Each line is created by code like the following:
>
> OUT logfile.txt
>
> Write 'something', .vsomethingelse
>
> OUT SCR
>
>
>
>
>
> Funny thing is sometimes the lines are separate and sometimes they are
> not.
>
> I looked at the file with a hex editor and the problem turns out to be
> missing LF (CHAR(10)) characters.
>
> CR (CHAR(13)) characters are still there.
>
>
>
> The code does not change, the computer has not changed.
>
> Some days it works correctly and some days it does not.
>
>
>
> Anyone ever seen this?
>
> Solution?
>
>
>
> Dennis McGrath
>
>

--- RBASE-L
================================================
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to [email protected]

(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: INTRO
================================================
TO UNSUBSCRIBE: 
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: UNSUBSCRIBE
================================================
TO SEARCH ARCHIVES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body, 
place any 
text to search for.
================================================

Reply via email to