Hi all,

I would appreciate if anyone that has worked with non-xml doc (like pictures etc.) storage, can share their wisdom / experiences with me. This is a follow up question to Storing and retrieving non-xml data.

I’m building an application that stores pictures from a folder, these pictures are then processed and then linked to a client. I’m using VB 6 and the activex API’s, is there a better way?

How do I store the data, do I need to have a seperate collection / doc that stores the information about the non-xml or can I combine them in one?
How do I search for docnames, how do I find the ino:id’s?
How do I delete the document?
The documentation is rather vague on these issues.

Thanks Jean

Hi Jean,

i

Hi all.

My TSD for 3-d versions of Tamono and TSD:

<?xml version = "1.0" encoding = "UTF-8"?>
<xs:schema xmlns:tsd = “http://namespaces.softwareag.com/tamino/TaminoSchemaDefinition” xmlns:xs = “XML Schema”>
xs:annotation
xs:appinfo
<tsd:schemaInfo name = “DCMSXMLchema”>
<tsd:collection name = “DCMXML”></tsd:collection>
<tsd:doctype name = “DCMXML”>
tsd:logical
tsd:contentopen</tsd:content>
</tsd:logical>
</tsd:doctype>
tsd:adminInfo
tsd:created2003-05-05T15:11:14.031-08:00</tsd:created>
tsd:modified2003-05-05T15:11:14.031-08:00</tsd:modified>
tsd:versionTSD3</tsd:version>
</tsd:adminInfo>
</tsd:schemaInfo>
</xs:appinfo>
</xs:annotation>
<xs:element name = “DCMXML”>
xs:complexType
<xs:choice minOccurs = “0” maxOccurs = “unbounded”>
<xs:element name = “EntryID” type = “xs:string”></xs:element>
<xs:element name = “LoginName” type = “xs:string”></xs:element>
<xs:element name = “PassWord” type = “xs:string”></xs:element>
<xs:element name = “Date_Time” type = “xs:string”>
xs:annotation
xs:appinfo
tsd:elementInfo
tsd:physical
tsd:native
tsd:index
tsd:standard</tsd:standard>
tsd:text</tsd:text>
</tsd:index>
</tsd:native>
</tsd:physical>
</tsd:elementInfo>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name = “From” type = “xs:string”>
xs:annotation
xs:appinfo
tsd:elementInfo
tsd:physical
tsd:native
tsd:index
tsd:standard</tsd:standard>
tsd:text</tsd:text>
</tsd:index>
</tsd:native>
</tsd:physical>
</tsd:elementInfo>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name = “Theme” type = “xs:string”>
xs:annotation
xs:appinfo
tsd:elementInfo
tsd:physical
tsd:native
tsd:index
tsd:text</tsd:text>
</tsd:index>
</tsd:native>
</tsd:physical>
</tsd:elementInfo>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name = “Text” type = “xs:string”>
xs:annotation
xs:appinfo
tsd:elementInfo
tsd:physical
tsd:native
tsd:index
tsd:text</tsd:text>
</tsd:index>
</tsd:native>
</tsd:physical>
</tsd:elementInfo>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name = “AppendURI” type = “xs:anyURI”></xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:schema>

But I had undestanded problems with 4-d versions of Tamino and TSD for previos schema.

My TSDs for 4-d versions of Tamono and TSD:

<?xml version = "1.0" encoding = "UTF-8"?>
<xs:schema xmlns:tsd = “http://namespaces.softwareag.com/tamino/TaminoSchemaDefinition” xmlns:xs = “XML Schema”>
xs:annotation
xs:appinfo
<tsd:schemaInfo name = “DCMSXMLchema”>
<tsd:collection name = “DCMXML”></tsd:collection>
<tsd:doctype name = “DCMXML”>
tsd:logical
tsd:contentopen</tsd:content>
</tsd:logical>
</tsd:doctype>
tsd:adminInfo
tsd:created2003-05-05T15:11:14.031-08:00</tsd:created>
tsd:modified2003-05-05T15:11:14.031-08:00</tsd:modified>
tsd:versionTSD4</tsd:version>
tsd:server4.1.1.1</tsd:server>
</tsd:adminInfo>
</tsd:schemaInfo>
</xs:appinfo>
</xs:annotation>
<xs:element name = “DCMXML”>
xs:complexType
<xs:choice minOccurs = “0” maxOccurs = “unbounded”>
<xs:element name = “EntryID” type = “xs:string”></xs:element>
<xs:element name = “LoginName” type = “xs:string”></xs:element>
<xs:element name = “PassWord” type = “xs:string”></xs:element>
<xs:element name = “Date_Time” type = “xs:string”>
xs:annotation
xs:appinfo
tsd:elementInfo
tsd:physical
tsd:native
tsd:index
tsd:standard</tsd:standard>
tsd:text</tsd:text>
</tsd:index>
</tsd:native>
</tsd:physical>
</tsd:elementInfo>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name = “From” type = “xs:string”>
xs:annotation
xs:appinfo
tsd:elementInfo
tsd:physical
tsd:native
tsd:index
tsd:standard</tsd:standard>
tsd:text</tsd:text>
</tsd:index>
</tsd:native>
</tsd:physical>
</tsd:elementInfo>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name = “Theme” type = “xs:string”>
xs:annotation
xs:appinfo
tsd:elementInfo
tsd:physical
tsd:native
tsd:index
tsd:text</tsd:text>
</tsd:index>
</tsd:native>
</tsd:physical>
</tsd:elementInfo>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name = “Text” type = “xs:string”>
xs:annotation
xs:appinfo
tsd:elementInfo
tsd:physical
tsd:native
tsd:index
tsd:text</tsd:text>
</tsd:index>
</tsd:native>
</tsd:physical>
</tsd:elementInfo>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name = “AppendURI” type = “xs:anyURI”></xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:schema>

and

<?xml version='1.0' encoding='UTF-8'?>
<xs:schema xmlns:xs=‘XML Schema’
xmlns:tsd=‘http://namespaces.softwareag.com/tamino/TaminoSchemaDefinition’>
xs:annotation
xs:appinfo
<tsd:schemaInfo name=‘DCMnonXMLSchema’>
<tsd:collection name=‘DCMnonXML’/>
<tsd:doctype name=‘DCMnonXML’>
tsd:nonXML/
</tsd:doctype>
</tsd:schemaInfo>
</xs:appinfo>
</xs:annotation>
</xs:schema>
It’s all.

So long.