exists command - resolution

[Brian K. White]

----- Original Message ----- 
From: "Dennis Malen" <dmalen at malen.com>
To: "Kenneth Brody" <kenbrody at bestweb.net>
Cc: <filepro-list at lists.celestial.com>
Sent: Tuesday, December 07, 2004 6:09 PM
Subject: Re: exists command - resolution


> Ken,
>
> How do I export twice while sitting in a record? My only alternative that
> worked was to define another export. Close the first, then define the new
> export and export.
>
> When I opened and closed the same definition the header was over written.

I do it in @once but you could use your existing logic just as well.

I put one actual export command in the table, and make it a gosub that comes 
after an end command.

flowchart or psuedocode looks like this:


----top of table----
gosub exp
out(1)=1
out(2)=23
...
out(14)=aa
end

exp:
export word ...
end

@once:
gosub exp
out(1)="Name"
out(2)="Rank"
...
out(14)="Serial Number"
end
----end of table---



In your case I would start with the above layout, and insert the exists test 
at the top of @once, before the "gosub exp" that tests true if the file 
exists then end (skipping the rest of @once in that case)
so the new table looks like:

----top of table----
gosub exp
out(1)=1
out(2)=23
...
out(14)=aa
end

exp:
export word (@pm) ...
end

@once:
if: exists(@pm) eq "0"
then: end
gosub exp
out(1)="Name"
out(2)="Rank"
...
out(14)="Serial Number"
end
----end of table---


> Dennis Malen
> ----- Original Message ----- 
> From: "Kenneth Brody" <kenbrody at bestweb.net>
> To: "Dennis Malen" <dmalen at malen.com>
> Cc: <filepro-list at lists.celestial.com>
> Sent: Tuesday, December 07, 2004 5:43 PM
> Subject: Re: exists command - resolution
>
>
>> Dennis Malen wrote:
>> [...]
>> > Problem: The header was not being created only the info on the file. 
>> > The
>> > header was suppose to run first then the info on the file.
>>
>> Actually, the _symptom_ was that the header record wasn't in the file.
> Why
>> it wasn't there was the reason for the previous thread.
>>
>> > Resolution: It was only after numerous communications with the list 
>> > that
> Brian
>> > White indicated he had a similar problem once. That was that the header
> was
>> > being over written. Upon further investigation and implementation that
> is
>> > exactly what had occurred. The "exists" command was working fine.
>>
>> I don't see how an exported record can be overwritten without closing and
>> re-opening the file.  Perhaps what you were doing was filling in the
> export
>> fields twice, rather than exporting two records?
>>
>> > I redefined the import command using a different file identifier 
>> > (export
> ASCII
>> > ???? =). That allowed me to open and close two different definitions
> (export
>> > commands) and write to the same file while remaining in the same
> record..
>> >
>> > Remember, because I had to write a header (one time when the file did
> not
>> > exists or upon creation) I was making two passes while in the pertinent
>> > record. The two different definitions avoided the header from being
>> > overridden.
>>
>> Exporting a header record is a very common task, and it does not need
>> you to use two separate exports.  Simply export two records the first
>> time through.
>>
>> [...]
>>
>> -- 
>>
> +-------------------------+--------------------+----------------------------
> -+
>> | Kenneth J. Brody        | www.hvcomputer.com |
> |
>> | kenbrody/at\spamcop.net | www.fptech.com     | #include
> <std_disclaimer.h> |
>>
> +-------------------------+--------------------+----------------------------
> -+
>> Don't e-mail me at: <mailto:ThisIsASpamTrap at gmail.com>
>>
>>
>>
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>