Albert and Jim,

Thanks for the feedback. So I have some rework/redesign to do. Sometimes it 
just takes the right events to teach you what you do not know. It will not be 
the last time.

Tom Frederick

From: [email protected] [mailto:[email protected]] On Behalf Of 
Jim Belisle
Sent: Thursday, April 21, 2016 12:41 AM
To: [email protected]
Subject: RE: [RBASE-L] - Using Notes

 

Albert,

 

Though I did not send the question and we have not had the problem caused by 
notes as was mentioned, your response has made me look into my tables to see if 
that might be a problem in the future. Thanks for the reply. When things go 
smoothly, it is easy to forget that there are limitations in certain areas that 
one has to take into consideration. 

 

James Belisle

 

Making Information Systems People Friendly Since 1990

cid:[email protected]

 

From: [email protected] [mailto:[email protected]] On Behalf Of 
Albert
Sent: Wednesday, April 20, 2016 9:18 PM
To: [email protected]
Subject: Re: [RBASE-L] - Using Notes

 

Sorry for the late reply, Tom. I've been working out of the office for a few 
days. 

I think my 2003 comments relate way back to earlier versions, but I suspect 
that putting several note columns into a table can easily exceed the row length 
limits, and that in turn can cause no end of problems, as you are finding out. 

It is quite easy to add Notes as a subsidiary table to any table. With R:Base 
forms, it is easily done to add a page or tab to the form that will open the 
notes. You might have an Invoice table with a bunch of information in it, and 
users may wish to note certain things. You can add any number of individual 
notes to a table that consists solely of InvoiceNo, User, Date, and Remarks. 
This format for the subsidiary table allows an almost infinite number of notes 
to be made against an invoice, and they can be retrieved in reverse order by 
date when editing the invoice. 

EDIT USING InvoiceEdit WHERe.. ARRANGE InvoiceNotes by InvoiceNoteDate DESC. 

I hope that helps!
Albert

On 2016-04-19 10:12 PM, tfred wrote:

I have become very focused on our use (probably overuse) of Notes. Our database 
is used every day and is very text heavy. In single-user mode it just works and 
keeps going. In multi-user mode, the exact same database will eventually close 
all users at the same time for no obvious reason or time. We have tried all 
kinds of adjustments, reloads, updates, and followed suggestions from this 
group.  We have  X Enterprise and have always used the 64 versions through the 
various versions. I often use 2-3 notes in tables. Some have up to 10. I 
probably have several hundred Notes in the tables of our system. Why? Because 
it always worked as I developed our system in single user mode. Never dawned on 
me that could be a problem in multi-user mode because it works most of the 
time. Now, after finding rbase-l emails from Albert Berry back in 2003 and Jan 
Johansen about putting Notes into their own tables, I think I finally 
understand how I can greatly exceed 4,092 bytes in a row with several large 
Notes. I read the discussions of  broken pointers which is still vague to me. I 
understand  the differences of Text vs. Notes vs. VarChar. Using ‘SELECT 
MAX(SLEN(column)) FROM table’ and related  statements, I can see there are many 
Notes I can convert to Text because users simply do not write much while other 
items (report Summaries can easily exceed 8,000 characters) should be in their 
own table. Can exceeding the Notes capacity in a row cause system closure 
problems?

 

Tom Frederick 

-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" 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.

 

-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" 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.

-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" 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.

-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" 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