Hopefully, this will pesent better! New to posting!
6898 8140010.8301.0.4215.4126.96.36.199 31-JUL-07 55999.8310.01 0.00 3,392.27
6899 8460010.6505.004915.4215.3188.8.131.52 31-JUL-07 529804.8415.01 0.00 867.76
6900 8460010.6505.004915.4215.3184.108.40.206 31-JUL-07 529804.8415.02 11,350.60 0.00
6901 8460010.7101.004915.4225.4220.127.116.11 31-JUL-07 45200.8415.01 634,297.53 0.00
6902 8460010.8301.004915.4215.418.104.22.168 31-JUL-07 55999.8415.02 30,660.60 0.00
6903 8460010.8301.004915.4215.422.214.171.124 31-JUL-07 55999.8415.01 62,490.66 0.00
6905 8910010.8101.0.4215.4126.96.36.199 31-JUL-07 55999.8620.01 0.00 189,304.37[/CODE]
Hi Bill, and welcome to the forum!
You're really close to the solution. Your idea of initially capturing the whole thing as one big field is a good one, so do that.
I did, and named that field "A", for convenience. Then you need to build eight calculated fields to break the A field apart properly. Each of the calculated fields (each defined to be character type) will have a similar expression. The first segment will have:
the next will have:
and so on, incrementing the last value by one, up to the last, which will be:
Have a look at LSplit in the online help. It has a related function that you may use some other time as well, RSplit.
I played a bit with the floating trap selector and hopefully found a combination.
1. Please choose the first line of the sample report as an example line.
2. Then copy the following line into your trap line:
ß . . . . . . . ß ßß . . ß ß /CODE
(The trap line should become yellow.)
3. Finally click on the button for the automatic field definition.
Hope this will work.
But I have the feeling, that the solution from Data Kruncher is more safe.
Worked perfectly. Will save me a great deal of time and I am glad to get away from the Text to Columns approach.
Will try the "floating suggestion" when time permits as I can certainly benefit from expanding my knowledge of this excellent product. First started to use it in the DOS days and have used the various versions over the years.
Thanks for the very quick response and excellent suggestions. Feeling spoiled!
Glad to hear that it works well for you.
The idea of doing as much as possible within Monarch, instead of Excel, is a bit of an extension on the topic of [URL="http://********************/tips/performing-analysis-work-with-monarch"]performing analysis work with Monarch[/URL] that I posted on my site a little while back.
Thanks for the update on your progress.