Using a "." in a description texted based field in AREV (AREV Specific)
At 20 APR 2000 05:12:22PM Dave Pointer wrote:
I hate to ask such a moronic question but there is a debate going on where I work. We have been using Arev since '84, and in our Product file, we have a description field that is used to enter text descriptions. The current debate is that entering data like this "Wash. Lrg. Eggs" will cause the system to crash, or cause difficulty sorting, and/or corrupt the database to the point it can't be accessed. It is important to note that we have entered data like this since '84 with no problems, but apparently I need more proof. If anyone can wiegh in with there knowledge on this, it would be most grateful. Thank you for your time-
Dave
ironpawn@hotmail.com
At 20 APR 2000 08:26PM Eric Emu wrote:
As an emu I should know - Wash. Lrg. Eggs. is perfectly safe to do in any AREV field.
Eric
At 20 APR 2000 11:02PM Dale Walker wrote:
I have used Rev G, Arev1.0 thru 3.12. I have a large genealogical database with more than one word in a field. For example the given names of my wife's grandmother is Ida Sofie Mina Karolina Kirstian Frederika. This field is indexed on given names as well as surnames. My System does not crash.
Dale
At 20 APR 2000 11:05PM Dale Walker wrote:
I have used Rev G, Arev1.0 thru 3.12. I have a large genealogical database with more than one word in a field. For example the given names of my wife's grandmother is Ida Sofie Mina Karolina Kirstian Frederika. This field is indexed on given names as well as surnames. My System does not crash.
Dale
ps. I use other characters that is possible as delimiters. I think that this is the issue here. When you set up a cross refed field certain characters are excluded. Also, the field delimiter in arev is ascii 254 as opposed to commas, etc.
Dale
At 21 APR 2000 02:04AM Richard Hunt wrote:
I have never had a problem using all the characters on the keyboard. I have never heard of such a problem. AREV is designed to handle all ASCII codes, 0 thru 255.
See… a compiled program can contain all 256 possible ASCII codes.
I would strongly suggest not to use the codes 250 thru 255. They are used to delimit values.
At 21 APR 2000 11:02AM Warren wrote:
A period (.) is a perfectly legal character in alphanumberic entry fields in Window entry screens, scribe, RBASIC INPUT etc. The only time it will make a difference is if the field/column is cross-referenced with the the period (.) designated as an additional delimiter. Even in this case it will not cause ARev to crash.
I think they are confused with 3.x's adherence to SQL standards requiring use of underscores (_) versus periods (.) for descriptor names. ARev 3.x may complain when you use a period inappropriately but it will not crash.