7/17/2009 8:48 PM
I have been having difficulty in getting some of my imports to be
recognized correctly as either keystrokes or data.
1. One of my data
columns contains ** in some of its records. FDL automatically
recognizes this as a shortcut. When I try to Mark Column as
Data it converts the selected fields as * (i.e. drops first *) and
makes column header read Data. If I then try to update the now
incorrect field from * to ** it turns the color code again to signify
ShortCut and changes the column header to read ShortCuts. Is this
all formatting as long as I don’t have a shortcut **. In other
words when entering data into my form will it enter ** or *?
2. In your
shortcut popup edit window you I think incorrectly state “A ShortCut
is recognized with a # character in the first position.”
3. When I import
\{ENTER} in a column it does not recognize it as a keystroke
originally. Somehow, in my process of trying to force it
formatted it correctly. Same with #50 not recognizing as delay.
Is this all formatting or will it not enter keystrokes into the form
correctly?
4. Because some
of my files contain 100,000+ records I don’t really want to just do
Fill Down as this takes extra time.
Many Thanks
1. One of my data columns contains ** in some of its records. FDL
automatically recognizes this as a shortcut. When I try to Mark Column as
Data it converts the selected fields as * (i.e. drops first *) and makes
column header read Data. If I then try to update the now incorrect field
from * to ** it turns the color code again to signify ShortCut and
changes the column header to read ShortCuts. Is this all formatting as
long as I don’t have a shortcut **. In other words when entering data
into my form will it enter ** or *?
If you need to send **
into the target application you can send it as a keystroke by entering
\** in the cell or you can define your own shortcut with any name and
enter the corresponding keystroke \** in the shortcut sheet for different
application types.
2. In your shortcut popup edit window you I
think incorrectly state “A ShortCut is recognized with a # character in
the first position.”
Yes you are right, it is incorrect and
we will correct it as soon as possible. Thanks for pointing out.
3. When I import \{ENTER} in a column it does not recognize it as a
keystroke originally. Somehow, in my process of trying to force it
formatted it correctly. Same with #50 not recognizing as delay. Is this
all formatting or will it not enter keystrokes into the form correctly?
Yes this is issue of formatting but have no effect in loading.
It will send correct keystrokes
4. Because some of my files
contain 100,000+ records I don’t really want to just do Fill Down as this
takes extra time.
It is advisable to divide the load into
manageable pieces by creating multiple Data Loader sheets rather than
having one big sheet.
© Interface Computers All Rights Reserved