Greg,
I'm lost. I thought that the input transform code WAS
the screening process. Can you discribe how these two
differ?
Thanks
Kevin
--- Gregory Woodhouse
[EMAIL PROTECTED] wrote:
This is hows Fileman sets screens on pointers.
Rather than edit the
input transform, you should modify the
The input transform is (usually) generated code. Rather than manually
set the screen in the input transform, you should specify the screen
(e.g., when creating the field) and let Fileman create the input
transform for you. Sometimes you need to create your own input
transform, but most of the
I should add that Fileman allows you to edit the input transform (and
sometimes this is precisely what you need to do), but there's a
downside: once the input transform becomes code that you write, Fileman
is no longer able to maintain it itself. If at a later time, you need
to modify the
I need help understanding an input transform
In file 50.7/PHARMACY ORDERABLE ITEM, in field MED
ROUTE (.06), I am being limited in the choices
available to me. I want to be able to put in ORAL or
PO for a drug route.
Here is a screen log:
INPUT TO WHAT FILE: PHARMACY ORDERABLE ITEM//
EDIT
This is hows Fileman sets screens on pointers. Rather than edit the
input transform, you should modify the screen.
Gregory Woodhouse
[EMAIL PROTECTED]
On Apr 23, 2005, at 6:46 PM, Kevin Toppenberg wrote:
I need help understanding an input transform
In file 50.7/PHARMACY ORDERABLE ITEM, in
