Separate embedded objects?

[jlockley]

I have a Pdx 8 query set up to export candidates and their resumes for specific tasks. Once I have pared down the resulting search table I would like to be able to view the resumes without opening and closing each separately from the individual records. Is there some way to view or extract them without the rest of the information? Obviously they are stored somewhere, but can they be accessed?

 

[Langley]

You could always display a report of the Answer.db table. That would allow you to navigate all the records in the format you want and even print it.

Mac
Mac

 

[jlockley]

Thanks Mac, but I haven't been able to put embedded objects in a report. I thought it wasn't possible. Am I doing something wrong? That would be terrific.

 

[Langley]

Maybe I don't understand the terminology you are using. What embedded object? I assumed the resume was in a memo or graphic field.

Mac
Mac

 

[jlockley]

Sorry. I keep documents Mostly in Word or WPD form as OLE objects in my records. I have not been able to place these in reports and have believed this not possible. Nor have I been able to get memo field contents in reports.

 

[Langley]

I can't help you with the OLE problem, but memo fields are easy to place in reports. First, don't use a table frame - just define the memo field as an field object in the record band; I usually put it under the other fields and make it wide enough to be easily read. Formatted memo fields might be better for resumes, as they tend to have bold and different sized text.
Mac

 

[jlockley]

Thanks. Unfortunately I can't store all the resumes in memo fields as some of the characters are routinely rejected. It would be terrific to export all of the documents to one file.

 

[Langley]

Just out of curiosity, what characters are rejected in the Formatted Memo field type? I have only used the regular memo fields as a rule (read: habit) but recently incorporated a formatted one into some new software I'm writing.
Mac

 

[jlockley]

Quotation marks for one. The long dash, I believe. Asterisks, if memory serves me right. Parentheses. Any of the odd characters which result from translating formated text into txt format. I can go through and look for non standard text characters on each resume I post, or I can just not post them into memo fields.

I have tried "straining" the material through clipmate (those of us with less knowledge often resort to guile), but it's a pain. I would need to reset the clipmate filter each time I use it, so that's out. Anyway, it's terrific to be able to search for a combined skill set then pull up the resume and send it to a client without having to reformat an ascii document.

Possibly related to this is the warning a check on table structure brings up: This field contains low ascii characters for alpha numeric fields. It's possible that the "low ascii characters" are what are being rejected.

 

[Langley]

Thanks for the information, I'll keep it in mind when I set up my picture values.

Mac

 

[jlockley]

A belated thanks to Mac, who's first answer here was absolutley on target. I just created a query and a report of nothing but the ole field containing documents. It either displays or prints the documents neatly. Very good.