Parsing lines in memo

[mohammadagul]

Hi,
Currently I have a scenario where we are requested by our corporate client to quote them of cost of Air Ticket to there required Destination.
Upon getting the email, we use our GDS System to book the flight. There upon the booked flight along with the fare is emailed to them. After sending the email the same data is copied in our database.

My users want to minimize their work. Before Sending the email to client they want to manually copy the data in one memo box. the data is as follows

NO NAMES
1 EK 7B 29JUN 5 DXBLHR SS1 0230 0700 /DCEK /E ADD ADVANCE PASSENGER INFORMATION SSR DOCS
AS PER EU REGULATIONS PAX CAN ADV EMERGENCY CTC IN SSR PCTC
2 PK 987C 30JUN 9 LHRISB SS1 0900 0900 /DCPK /EADD ADVANCE PASSENGER INFORMATION SSR DOCS
2F2B.2F2B*AGU 0038/04MAR12
WPNCB«
BASE FARE TAXES TOTAL
1- AED2800.00 80.00XT AED2880.00ADT
XT 75.00AE 5.00TP
2800.00 80.00 2880.00TTL ADT-01 B1SOWAE1
DXB EK LON Q30.00 729.64NUC759.64END ROE3.673
NON-END/SKYWARDS SAVER/
VALIDATING CARRIER - EK
2- AED2800.00 80.00XT AED2880.00ADT
XT 75.00AE 5.00TP
2800.00 80.00 2880.00TTL ADT-01 B1SOWAE1
DXB EK LON Q30.00 729.64NUC759.64END ROE3.673
NON-END/SKYWARDS SAVER/
VALIDATING CARRIER - PK
AIR EXTRAS AVAILABLE - SEE WP*AE

I want to keep only the red lines and remove the rest of the data either in the same memo box or in a different memo.

 

[mohammadagul]

hello, Any one..Any idea on this.

 

[missinglinq]

hello, Any one..Any idea on this.

Sorry that you've been awaiting a response for so long, but considering that 60 members have read your post and none have answered, my guess is that the answer would be 'no.'

Memo Fields have their uses, but that use is pretty much limited to entering 'free text,' if you will. 'Free text' being things like customer notes, narratives and, yes, memos. Memo Fields should never be used for Data where there is even the remotest possibility that said Data will ever have to be manipulated in any way, shape or form! That means no Sorting, Searching or Parsing! Data where this is a possibility really needs to be kept in distinctly separate Fields. This is sometimes referred to as the Atomic Theory of Data Storage.

Memo Fields have a very poor reputation, in Access, and almost all cases where I read about them causing problems can be directly related to developers trying to do these kind of things with them.

I don't, and I suspect no one else here, either, knows your particular business, so this is all Greek to us, but how would you ever separate out the Data in Red from all the surrounding Data?

I have no idea of how much control you have over the Data you're starting out with, but it really looks as if you've got the cart before the horse. It looks as if things like

1 EK 7B 29JUN 5 DXBLHR SS1 0230 0700 /DCEK /E
2 PK 987C 30JUN 9 LHRISB SS1 0900 0900 /DCPK /E
2880.00TTL
VALIDATING CARRIER - EK
VALIDATING CARRIER - PK

should start out in separate Fields and then be combined to get the block you're now starting out with.

Sorry, but unless you have some way of isolating the Data in Red from the rest of the block of information, I really don't see how anyone can help you.

Linq ;0)>