• To: "'ht@i... (Henry S. Thompson)'" <IMCEANOTES-ht+40inf+2Eed+2Eac+2Euk+20+28Henry+20S+2E+20Thompson+29@F...>, 'Chiusano Joseph' <chiusano_joseph@b...>, "'\"Phil Fuhlman\" <pfuhlman@D...>'" <IMCEANOTES-+22Phil+20Fuhlman+22+20+3Cpfuhlman+40Dexma+2Ecom+3E@F...>
• Subject: RE: Schema constructs
• From: "James, David" <david.james@i...>
• Date: Wed, 16 Jun 2004 06:04:52 -0400
• Cc: "'xml-dev@l...'" <xml-dev@l...>

Thank you all for your suggestions. I could nest my 'flexible' elements within another element but would prefer to avoid that if possible. I can use abstract types (which is better than the way I had started defining the structure) but that does not allow me to insist that the tag element is always first in the list. However, I could live with this. Defining the tag as an attribute is the neatest approach but does not allow me to use the automatic import capability of MS Access. But I will need to do some processing of the data anyway.

So I pay my money and take my choice. At least I now know that using xml is a viable option to my problem.

Regards,
David James

• Prev by Date: Re: Triplets on the Internet
• Next by Date: Re: Triplets on the Internet
• Previous by thread: Re: Schema constructs
• Next by thread: cdata
• Index(es):
  • Date
  • Thread