G
godiva
I'm a bit baffled as to why this even makes a difference. I have a
transfertext import delimited line. When a text box on the form is
populated with a file path including full file name to import (on
update of an option group on the form) A2k3 kicks out a message that
the file can't be imported. However, if I use the browse feature and
browse to the file, populating the same text box that way, it imports
it without a hitch. Punctuation, capitalization, everything matches.
So why is it that A2k3 gives me a talk to the hand with the prefilled
but is perfectly happy with the file name provided by browsing to it?
Also, what stick do I beat this with (i.e. how do I fix this? the
client is a bit lazy and doesn't want to browse to the file *rolls
eyes*)
transfertext import delimited line. When a text box on the form is
populated with a file path including full file name to import (on
update of an option group on the form) A2k3 kicks out a message that
the file can't be imported. However, if I use the browse feature and
browse to the file, populating the same text box that way, it imports
it without a hitch. Punctuation, capitalization, everything matches.
So why is it that A2k3 gives me a talk to the hand with the prefilled
but is perfectly happy with the file name provided by browsing to it?
Also, what stick do I beat this with (i.e. how do I fix this? the
client is a bit lazy and doesn't want to browse to the file *rolls
eyes*)