key field - newbie # 11 (OpenInsight 32-bit Specific)
At 26 APR 2010 02:08:57PM ronald brown wrote:
Hi All,
newbie question # 1
I'm a newbie to OI. Just purchased OI 9.1 and have some questions that I generated going thru documentation, the website and just trying some things.
I will post each as a new topic, so that they can be treated individually.
TIA for helping with your ideas, suggestions and comments.
Running OI 9.1, on a win xp client. The server is a windows 2000 server box, running Unidata, and an application called Manage 2000.
I have a Unidata table, where the key to the table is formatted with some characters (alpha and numeric) followed by the pipe symbol (|), followed by 2 numbers. When I initially create a form, I can enter a part number and see the data, i.e. ABC5001|03. But I have 2 issues…
If I save and close the form designer, then reopen that form and try entering ABC5001|03, I always get an error message regarding the key field…sorry, I wasn't smart enough to put the error message in my notes.
If I try to put a check for the format, i.e. 19Z"|"2N or 19Z'|'2N in the field definition, then try to do an entry, I always get the error that my entry must be 19 characters followed by "" followed by 2 numbers. The pipe symbol does not show in the resulting error message.
In the documentation, it says that a wide range of chaaracters can be used for key fields.
thanx,
ron
At 26 APR 2010 03:01PM DSig (SigSolutions) wrote:
My guess is that PIPE will be a problem as it is used in other in things like pattern match etc (if i remember correctly).
One of the worst problems with *smart* part numbers.
At 26 APR 2010 04:32PM ronald brown wrote:
I also saw something about pattern matching with double pipes.
I'll have to come up with something, since our entire database is built around part numbers that contain the part, the pipe, and the facility they reside in.
thanx for your help,
ron
At 26 APR 2010 10:55PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
You could use a custom conversion. In RBasic you can write your own Iconv/OConv processors and reference them using MYCONVROUTINENAME. Write as a subroutine taking four parameters, Type, Passed, Label and Returned. See help under "User Defined Conversions".
World leaders in all things RevSoft
At 27 APR 2010 01:05PM ronald brown wrote:
Thank you. I will look at the docs, and see what I can do.
ron