Warning
-
Interesting you see a working solution as a problem!
My suggestion will work even when end-users decide to broaden the column size and send 130 char width instead of 90 char.
If this will be the case, OP solution of having 3 tables with 7000 char width will not work anymore. He then have to rethink and maybe create 4 or 5 tables of 7000 char width and import file accordingly in order to not clip information.
The approach of using a TEXT solves that in one step. I can imagine that the data is separated by spaces or similar so parsing the TEXT column would be easy.
And again, we do not know how often this import is made.
N 56°04'39.16"
E 12°55'05.25" -
Hi Ed,
As an escapee from the NHS asylum i know your pain
As a matter of interest what will your reaction be when they ask for it to be printed on 1 A4 page and then complain they can't read it!!
My fists still itch when i think about that place.
K.
-
I think I would either clip them behind the ear or curl up into a little ball and start sobing
-
My system generates every day 3 reports 150+ columns each.
It's not for printing, it's for feeding some freaky software. It needs 4 columns just for date: MM, DD, CC(century), YY.
And I never came even close to the limit.
It's obvious you don't need 100 or 50 characters to pass 2 digits DD. You never need more than varchar(9) for integer values, datetime or money will never exceed varchar(20), etc.
You never gonna reach 8060 bytes limit in 90 columns report if you think about it when building the report.
_____________
Code for TallyGenerator
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply