| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
What would you expect to happen in the following senario.
1.create a wps boiler plate that contains the following and put it in the
Users ALL-IN-1 Sub-directory and call it call.txt:
<&include #idea>
this is boiler plate text
<&include #benefit>
2.create a file called b.txt in the Users ALL-IN-1 Sub-directory
3.create a .scp which contains the following:
get #idea = "a.txt"
get #benefit = "b.txt"
list<merge call.wpl
The list<merge does not display anything after the <&include #idea>
Why?
If the file a.txt exist there is no problem. Will probably SPR this
but does anyone have a answer as to Why?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 626.1 | Seen that, done that (but didn't report it) | BUFFER::VICKERS | Perfect is the enemy of good | Mon May 11 1992 04:31 | 27 |
I encountered this behaviour several months ago when helping a customer
with ALL-IN-1 EARS but, of course, never thought to report it so that
it would behave in a more sensible manner. I apologize for being such
a clod (in this particular matter, at least ;').
The approach that I took at that time was to check for the file being
there in the template:
Below is the include of #FUBAR which is defined as "<#FUBAR>":
<&OA .if oa$dir:"*.*;".%whole[#fubar] nes "" then <->
get oa$merge_line = "<&include #fubar>" else <->
get oa$merge_line = "There is no such file">
End of "<#FUBAR>"
I suspect that you have already done that, of course.
My recollection was that if there was a null filename, .;, in the
user's default directory it would be included. I just tried this and
the null filename was not processed. I am certain that there was some
sort of file being picked up as the 'feature' was discovered in a
rather embarrassing manner as the MIS directory had such a null file
(or other special name) in which was the salary plan for the
organization. As you can imagine, it was not giving him good
vibrations about this information appearing in a 'random' manner.
Have fun,
don
| |||||
| 626.2 | KERNEL::COOPER | Suzanne Cooper UK Customer Support (833)3502 | Mon May 11 1992 10:15 | 7 | |
Thanks for replying, I think we worked round it with "if the file
doesn't exist then create a empty one" type syntax
I SPR'd it as well
Suzanne
| |||||