I think the issue is that you want to use a Fileman API on the file of
files. File 1 is the file of files. I do not think that Fileman will care
if the individual files have data in them. If the fields have been defined
for the individual files that is what the API's can retrieve for you. When
you are looking at file 1 then the individual file numbers are the IEN's of
the individual records of the file of files. You can also use Fileman API's
on the data dictionary which has been called File 0. However, you cannot 0
(zero) as the file number. You have to use the actual global root. I hope
this makes sense.
Jim Gray
----- Original Message -----
From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, July 11, 2005 9:13 AM
Subject: Re: [Hardhats-members] Data dictionary question...
A list of fields from a file IS what I want. And this
GETS^DIQ is a bit off target in that it gets actual
values (meaning that there must be at least one record
in the file file for it to work). But this would give
a list of the fields in the resulting array.
Actually, now that I think about it, I doubt that it
will return the name of a field if there is no data in
that field. So perhaps this function wouldn't work
after.
Perhaps there remains a need for another function in
the API to list the names of fields in file.
Thanks
Kevin
--- Gregory Woodhouse
<[EMAIL PROTECTED]> wrote:
Well, this is a little different from your stated
requirement.
Without knowing the fields in your file, you can use
"*" or "**" to
get all the field values for a *file entry*. If you
are serializing
file entries using XML, that may be exactly what you
want). But you
asked for something else. You asked for a way to get
a list of fields
in a *file*. That's why it took so long.
===
Gregory Woodhouse
[EMAIL PROTECTED]
"Perfection is achieved, not when there is nothing
more to add, but
when there is nothing left to take away."
-- Antoine de Saint-Exupery
On Jul 11, 2005, at 7:48 AM, Kevin Toppenberg wrote:
> Well I am glad to see that this need has been
filled
> with a proper API.
>
> I does seem a bit suspicious that it took over a
week
> for someone to come up with the appropriate
function
> (thanks Bob). The names in the API are often less
> than helpful.
>
> Thanks everyone
> Kevin
>
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With
Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to
explore the latest in dual
core and dual graphics technology at this free one
hour event hosted by HP,
AMD, and NVIDIA. To register visit
http://www.hp.com/go/dualwebinar
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
____________________________________________________
Sell on Yahoo! Auctions - no fees. Bid on great items.
http://auctions.yahoo.com/
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar
happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by
HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
