Hi Tony,
Thanks for your thoughts. In this case, however, the report option
would not be ideally suited. With upload files for annual 1099 and
W-2 reports for example, each row of specific length has to be
filled in with various data items in specific columns. So, m
Steve,
Thanks for the suggestion. I will definitely try ASCII 255 and see
what happens.
--
James
On 11/4/2023 12:41 PM, Steve Sweeney
wrote:
ASCII 255 is anothe
Bruce,
Yes, I would second the enhancement requests for SET TRIM ON/OFF
and/or (NTRIM(text)) function. But for now I am hopeful that
char(160) might solve some of the issues I had. Government upload
file specifications typically say "blank space" without wh
Hello James,
Maybe it is an idea to have a look at the report possibilities.
Print a report as a txt file is possible and there are a lot of options
available.
open the report designer and choose for File | Print to Text File Setup
There you are able to create a TXT file in the way you like
ASCII 255 is another option for a hard space.
Steve
From: rbase-l@googlegroups.com On Behalf Of Bruce
Chitiea
Sent: Saturday, November 4, 2023 9:39 AM
To: rbase-l@googlegroups.com
Subject: Re[2]: [RBASE-L] - creating text file with blank spaces in tact
James:
In broader context, I cannot swe
James:
In broader context, I cannot swear that (CHAR(160)) serves as a "hard
space" across the entire family of True Type fonts likely being used by,
say Lacerte.
But I'm guessing you're not the only one tormented by gov't
punch-card-era data formats.
So, maybe try an enhancement request (
I was mainly trying out different values. Over the years, I have been
using mixture of methods developed ad hoc to handle federal and state
government uploads. I have been alternating between char(00) and
char(32). Now, I am trying to figure out something that works reliably
on all submissions
7 matches
Mail list logo