|
 |
ado_dotnet thread: Persisting a new dataset to a database
Message #1 by "Gary Minor" <Gary@C...> on Wed, 23 Jan 2002 23:38:43 -0500
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0005_01C1A467.18BF9500
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
I need to build a dataset programmatically, and then save it as a
Microsoft Access file.
I know how to fill a DataSet from a database or load it from an XML
file.
I know how to update a database from a DataSet or write an XML file from
a DataSet.
But I can't make a new database from a DataSet.
I think the ability to create a new Access database from a DataSet is
basic to Microsoft's strategy.
At the very least, I would expect to be able to create a new table in an
existing database from a table in a DataSet.
There are several cases where this is needed.
1) An existing database needs to be sent over the Web. The
originator would use ADO.net to create a DataSet and then send it as
XML. The receiver would use the XML to create a DataSet and save it as a
database
2) A new DataSet is created from a complex SQL statement
(selections and joins) and then the result is used to make a new table
in the database.
3) A new DataSet is created programmatically from some exotic
source. This may include several tables, relationships and constraints.
Then the DataSet needs to be saved as a database.
This should be possible without having pre-knowledge of the column
headings or the data types.
I have searched through Wrox's Professional ADO.NET Programming, in
particular the chapters "Using the DataAdapter", "Typed DataSets and
DataSet Schemas", and "Mapping". Perhaps the answer is there, but I
can't find it.
DAO has the ability to create a database programmatically. I don't know
about ADO. Should I go back to DAO to do this?
Microsoft may argue that the DataSet can be saved as XML and therefore
the dataset representation is not needed. The counter argument is that
the XML can't be the operated on with SQL statements. Microsoft may then
argue that an XML file can be operated on for the same results, but with
different techniques.
Help or comments, anyone?
Gary Minor
Controlware
Message #2 by Richard Ainsley <rainsley@p...> on Wed, 23 Jan 2002 22:14:56 -0800
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0148_01C1A45B.6399FD60
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
DAO is the native driver for the JET databases that Access normally
uses. The ability to create a database is not part of standard SQL (you
can create tables with ANSI SQL however). I suspect unless you are
willing to run ACCESS remoely or a VB6 app remotely or use DAO in a
wrapper directly; that you might want to consider something like copying
an empty JET database to a file with a different name and then using the
newly created JET *.mdb file as you "new" JET database. That would be
considerably easier than fighting the incompatibilities you are certain
to discover using the alternatives at this point in time.
Once you have a database there are DML SQL statements you can build as
command text that can create tables.
Table creation syntax is:
"Create Table table_name (col_name1 type1 [NOT NULL | NULL],
col_name2... )"
You can build the create table sql syntax from information stored in the
dataset you have. Each field has properties such as name, type, length,
nullable etc.
place the commandtext in a oleDB.oleDBCommand object together with an
open oledb.oledbConection object then invoke the ExecuteNonQuery method
on the command object.
Good luck.
----- Original Message -----
From: Gary Minor
To: ADO.NET
Sent: Wednesday, January 23, 2002 8:38 PM
Subject: [ado_dotnet] Persisting a new dataset to a database
I need to build a dataset programmatically, and then save it as a
Microsoft Access file.
I know how to fill a DataSet from a database or load it from an XML
file.
I know how to update a database from a DataSet or write an XML file
from a DataSet.
But I can't make a new database from a DataSet.
I think the ability to create a new Access database from a DataSet is
basic to Microsoft's strategy.
At the very least, I would expect to be able to create a new table in
an existing database from a table in a DataSet.
There are several cases where this is needed.
1) An existing database needs to be sent over the Web. The
originator would use ADO.net to create a DataSet and then send it as
XML. The receiver would use the XML to create a DataSet and save it as a
database
2) A new DataSet is created from a complex SQL statement
(selections and joins) and then the result is used to make a new table
in the database.
3) A new DataSet is created programmatically from some exotic
source. This may include several tables, relationships and constraints.
Then the DataSet needs to be saved as a database.
This should be possible without having pre-knowledge of the column
headings or the data types.
I have searched through Wrox's Professional ADO.NET Programming, in
particular the chapters "Using the DataAdapter", "Typed DataSets and
DataSet Schemas", and "Mapping". Perhaps the answer is there, but I
can't find it.
DAO has the ability to create a database programmatically. I don't
know about ADO. Should I go back to DAO to do this?
Microsoft may argue that the DataSet can be saved as XML and therefore
the dataset representation is not needed. The counter argument is that
the XML can't be the operated on with SQL statements. Microsoft may then
argue that an XML file can be operated on for the same results, but with
different techniques.
Help or comments, anyone?
Gary Minor
Controlware
$subst('Email.Unsub').
Message #3 by "Shane Berry" <spectrum@p...> on Thu, 24 Jan 2002 07:36:06 -0600
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_000D_01C1A4A9.C892B290
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Take a look at ADOX. It has some of the administration functionality
that DAO uses. In an application I have, I copy a empty mdb file and
then use ADOX to build tables, indexes, constraints, etc. This is not
an ADO.NET application, so I am not sure what will apply there.
-----Original Message-----
From: Richard Ainsley [mailto:rainsley@p...]
Sent: Thursday, January 24, 2002 12:15 AM
To: ADO.NET
Subject: [ado_dotnet] Re: Persisting a new dataset to a database
DAO is the native driver for the JET databases that Access normally
uses. The ability to create a database is not part of standard SQL (you
can create tables with ANSI SQL however). I suspect unless you are
willing to run ACCESS remoely or a VB6 app remotely or use DAO in a
wrapper directly; that you might want to consider something like copying
an empty JET database to a file with a different name and then using the
newly created JET *.mdb file as you "new" JET database. That would be
considerably easier than fighting the incompatibilities you are certain
to discover using the alternatives at this point in time.
Once you have a database there are DML SQL statements you can build as
command text that can create tables.
Table creation syntax is:
"Create Table table_name (col_name1 type1 [NOT NULL | NULL],
col_name2... )"
You can build the create table sql syntax from information stored in the
dataset you have. Each field has properties such as name, type, length,
nullable etc.
place the commandtext in a oleDB.oleDBCommand object together with an
open oledb.oledbConection object then invoke the ExecuteNonQuery method
on the command object.
Good luck.
----- Original Message -----
From: Gary Minor <mailto:Gary@C...>
To: ADO.NET <mailto:ado_dotnet@p...>
Sent: Wednesday, January 23, 2002 8:38 PM
Subject: [ado_dotnet] Persisting a new dataset to a database
I need to build a dataset programmatically, and then save it as a
Microsoft Access file.
I know how to fill a DataSet from a database or load it from an XML
file.
I know how to update a database from a DataSet or write an XML file from
a DataSet.
But I can't make a new database from a DataSet.
I think the ability to create a new Access database from a DataSet is
basic to Microsoft's strategy.
At the very least, I would expect to be able to create a new table in an
existing database from a table in a DataSet.
There are several cases where this is needed.
1) An existing database needs to be sent over the Web. The originator
would use ADO.net to create a DataSet and then send it as XML. The
receiver would use the XML to create a DataSet and save it as a database
2) A new DataSet is created from a complex SQL statement (selections and
joins) and then the result is used to make a new table in the database.
3) A new DataSet is created programmatically from some exotic source.
This may include several tables, relationships and constraints. Then the
DataSet needs to be saved as a database.
This should be possible without having pre-knowledge of the column
headings or the data types.
I have searched through Wrox's Professional ADO.NET Programming, in
particular the chapters "Using the DataAdapter", "Typed DataSets and
DataSet Schemas", and "Mapping". Perhaps the answer is there, but I
can't find it.
DAO has the ability to create a database programmatically. I don't know
about ADO. Should I go back to DAO to do this?
Microsoft may argue that the DataSet can be saved as XML and therefore
the dataset representation is not needed. The counter argument is that
the XML can't be the operated on with SQL statements. Microsoft may then
argue that an XML file can be operated on for the same results, but with
different techniques.
Help or comments, anyone?
Gary Minor
Controlware
$subst('Email.Unsub').
$subst('Email.Unsub').
Message #4 by KC.Lists.Net@C... on Thu, 24 Jan 2002 20:27:32
|
|
I've been tring to get an answer to that question from various lists too.
So, here I also sit and ponder the question with my datasets in memory
wanting to ceate .mdb files from them.
The best answer I've received so far is to, create a blank .mdb file and
save it as a resource in my assembly then persist it to disk whenever I
need one (This still creates an extra file, same as keeping a blank .mdb
file on disk and making copies of it when needed). All my code is in one
file, except framework .dll's, just my executable, that's all the files I
want there to be. There has to (should) be a way to persist a dataset to a
physical database file (that doesn't pre-exist). Seems that should be
intrinsic. Anyway, if you ever find out the answer, please share the
knowledge !
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_0005_01C1A467.18BF9500
> Content-Type: text/plain;
> charset="us-ascii"
> Content-Transfer-Encoding: 7bit
>
> I need to build a dataset programmatically, and then save it as a
> Microsoft Access file.
>
> I know how to fill a DataSet from a database or load it from an XML
> file.
> I know how to update a database from a DataSet or write an XML file from
> a DataSet.
> But I can't make a new database from a DataSet.
>
> I think the ability to create a new Access database from a DataSet is
> basic to Microsoft's strategy.
> At the very least, I would expect to be able to create a new table in an
> existing database from a table in a DataSet.
>
> There are several cases where this is needed.
> 1) An existing database needs to be sent over the Web. The
> originator would use ADO.net to create a DataSet and then send it as
> XML. The receiver would use the XML to create a DataSet and save it as a
> database
> 2) A new DataSet is created from a complex SQL statement
> (selections and joins) and then the result is used to make a new table
> in the database.
> 3) A new DataSet is created programmatically from some exotic
> source. This may include several tables, relationships and constraints.
> Then the DataSet needs to be saved as a database.
>
> This should be possible without having pre-knowledge of the column
> headings or the data types.
>
> I have searched through Wrox's Professional ADO.NET Programming, in
> particular the chapters "Using the DataAdapter", "Typed DataSets and
> DataSet Schemas", and "Mapping". Perhaps the answer is there, but I
> can't find it.
>
> DAO has the ability to create a database programmatically. I don't know
> about ADO. Should I go back to DAO to do this?
>
> Microsoft may argue that the DataSet can be saved as XML and therefore
> the dataset representation is not needed. The counter argument is that
> the XML can't be the operated on with SQL statements. Microsoft may then
> argue that an XML file can be operated on for the same results, but with
> different techniques.
>
> Help or comments, anyone?
>
> Gary Minor
> Controlware
>
>
>
> ------=_NextPart_000_0005_01C1A467.18BF9500
> Content-Type: text/html;
> charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> <html xmlns:o=3D"urn:schemas-microsoft-com:office:office"
> xmlns:w=3D"urn:schemas-microsoft-com:office:word"
> xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags"
> xmlns=3D"http://www.w3.org/TR/REC-html40">
>
> <head>
> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html;
> charset=3Dus-ascii">
>
>
> <meta name=3DProgId content=3DWord.Document>
> <meta name=3DGenerator content=3D"Microsoft Word 10">
> <meta name=3DOriginator content=3D"Microsoft Word 10">
> <link rel=3DFile-List href=3D"cid:filelist.xml@0...">
> <o:SmartTagType
> namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
> name=3D"City"/>
> <o:SmartTagType
> namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
> name=3D"place"/>
> <!--[if gte mso 9]><xml>
> <o:OfficeDocumentSettings>
> <o:DoNotRelyOnCSS/>
> </o:OfficeDocumentSettings>
> </xml><![endif]--><!--[if gte mso 9]><xml>
> <w:WordDocument>
> <w:SpellingState>Clean</w:SpellingState>
> <w:GrammarState>Clean</w:GrammarState>
> <w:DocumentKind>DocumentEmail</w:DocumentKind>
> <w:EnvelopeVis/>
> <w:Compatibility>
> <w:BreakWrappedTables/>
> <w:SnapToGridInCell/>
> <w:WrapTextWithPunct/>
> <w:UseAsianBreakRules/>
> </w:Compatibility>
> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
> </w:WordDocument>
> </xml><![endif]--><!--[if !mso]>
> <style>
> st1\:*{behavior:url(#default#ieooui) }
> </style>
> <![endif]-->
> <style>
> <!--
> /* Style Definitions */
> p.MsoNormal, li.MsoNormal, div.MsoNormal
> {mso-style-parent:"";
> margin:0in;
> margin-bottom:.0001pt;
> mso-pagination:widow-orphan;
> font-size:12.0pt;
> font-family:"Times New Roman";
> mso-fareast-font-family:"Times New Roman";}
> a:link, span.MsoHyperlink
> {color:blue;
> text-decoration:underline;
> text-underline:single;}
> a:visited, span.MsoHyperlinkFollowed
> {color:purple;
> text-decoration:underline;
> text-underline:single;}
> span.EmailStyle17
> {mso-style-type:personal-compose;
> mso-style-noshow:yes;
> mso-ansi-font-size:10.0pt;
> mso-bidi-font-size:10.0pt;
> font-family:Arial;
> mso-ascii-font-family:Arial;
> mso-hansi-font-family:Arial;
> mso-bidi-font-family:Arial;
> color:windowtext;}
> @page Section1
> {size:8.5in 11.0in;
> margin:1.0in 1.25in 1.0in 1.25in;
> mso-header-margin:.5in;
> mso-footer-margin:.5in;
> mso-paper-source:0;}
> div.Section1
> {page:Section1;}
> /* List Definitions */
> @list l0
> {mso-list-id:1502700684;
> mso-list-type:hybrid;
> mso-list-template-ids:-373920310 67698705 67698713 67698715
67698703
> 67698713 67698715 67698703 67698713 67698715;}
> @list l0:level1
> {mso-level-text:"%1\)";
> mso-level-tab-stop:.5in;
> mso-level-number-position:left;
> text-indent:-.25in;}
> @list l0:level2
> {mso-level-tab-stop:1.0in;
> mso-level-number-position:left;
> text-indent:-.25in;}
> @list l0:level3
> {mso-level-tab-stop:1.5in;
> mso-level-number-position:left;
> text-indent:-.25in;}
> @list l0:level4
> {mso-level-tab-stop:2.0in;
> mso-level-number-position:left;
> text-indent:-.25in;}
> @list l0:level5
> {mso-level-tab-stop:2.5in;
> mso-level-number-position:left;
> text-indent:-.25in;}
> @list l0:level6
> {mso-level-tab-stop:3.0in;
> mso-level-number-position:left;
> text-indent:-.25in;}
> @list l0:level7
> {mso-level-tab-stop:3.5in;
> mso-level-number-position:left;
> text-indent:-.25in;}
> @list l0:level8
> {mso-level-tab-stop:4.0in;
> mso-level-number-position:left;
> text-indent:-.25in;}
> @list l0:level9
> {mso-level-tab-stop:4.5in;
> mso-level-number-position:left;
> text-indent:-.25in;}
> ol
> {margin-bottom:0in;}
> ul
> {margin-bottom:0in;}
> -->
> </style>
> <!--[if gte mso 10]>
> <style>
> /* Style Definitions */
> table.MsoNormalTable
> {mso-style-name:"Table Normal";
> mso-tstyle-rowband-size:0;
> mso-tstyle-colband-size:0;
> mso-style-noshow:yes;
> mso-style-parent:"";
> mso-padding-alt:0in 5.4pt 0in 5.4pt;
> mso-para-margin:0in;
> mso-para-margin-bottom:.0001pt;
> mso-pagination:widow-orphan;
> font-size:10.0pt;
> font-family:"Times New Roman";}
> </style>
> <![endif]-->
> </head>
>
> <body lang=3DEN-US link=3Dblue vlink=3Dpurple
> style=3D'tab-interval:.5in'>
>
> <div class=3DSection1>
>
> <p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>I need to build a dataset
> programmatically, and then save it as a Microsoft Access
> file.<o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-
family:Arial'><o:p> </o:p></span></fo
> nt></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>I know how to fill a
> DataSet from a
> database or load it from an XML file.<o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>I know how to update a
> database from
> a DataSet or write an XML file from a
> DataSet.<o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>But I can’t make a
> new
> database from a DataSet.<o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-
family:Arial'><o:p> </o:p></span></fo
> nt></p>
>
> <p class=3DMsoNormal style=3D'text-indent:.5in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>I think the ability to
> create a new
> Access database from a DataSet is basic to Microsoft’s
> strategy.<o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal style=3D'text-indent:.5in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>At the very least, I would
> expect to
> be able to create a new table in an existing database from a table in a
> DataSet.<o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal><font size=3D2 face=3DArial><span
> style=3D'font-size:10.0pt;
> font-family:Arial'><o:p> </o:p></span></font></p>
>
> <p class=3DMsoNormal style=3D'text-indent:.25in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>There are several cases
> where this
> is needed.<o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal
> style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1;
> tab-stops:list .5in'><![if !supportLists]><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial;mso-fareast-font-
family:Arial
> '><span
> style=3D'mso-list:Ignore'>1)<font size=3D1 face=3D"Times New
> Roman"><span
> style=3D'font:7.0pt "Times New
> Roman"'>
> </span></font></span></span></font><![endif]><font
> size=3D2 face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>An existing
> database needs to be sent over the Web. The originator would use ADO.net
> to
> create a DataSet and then send it as XML. The receiver would use the XML
> to
> create a DataSet and save it as a database<o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal
> style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1;
> tab-stops:list .5in'><![if !supportLists]><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial;mso-fareast-font-
family:Arial
> '><span
> style=3D'mso-list:Ignore'>2)<font size=3D1 face=3D"Times New
> Roman"><span
> style=3D'font:7.0pt "Times New
> Roman"'>
> </span></font></span></span></font><![endif]><font
> size=3D2 face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>A new
> DataSet is created from a complex SQL statement (selections and joins)
> and then
> the result is used to make a new table in the
> database.<o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal
> style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1;
> tab-stops:list .5in'><![if !supportLists]><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial;mso-fareast-font-
family:Arial
> '><span
> style=3D'mso-list:Ignore'>3)<font size=3D1 face=3D"Times New
> Roman"><span
> style=3D'font:7.0pt "Times New
> Roman"'>
> </span></font></span></span></font><![endif]><font
> size=3D2 face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>A new
> DataSet is created programmatically from some exotic source. This may
> include
> several tables, relationships and constraints. Then the DataSet needs to
> be
> saved as a database.<o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-
family:Arial'><o:p> </o:p></span></fo
> nt></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>This should be possible
> without
> having pre-knowledge of the column headings or the data
> types.<o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-
family:Arial'><o:p> </o:p></span></fo
> nt></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>I have searched through
> Wrox’s
> Professional ADO.NET Programming, in particular the chapters
> “Using the
> DataAdapter”, “Typed DataSets and DataSet Schemas”,
> and
> “Mapping”. Perhaps the answer is there, but I can’t
> find it. <o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-
family:Arial'><o:p> </o:p></span></fo
> nt></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>DAO has the ability to
> create a
> database programmatically. I don’t know about
> </span></font><st1:City><st1:place><font
> size=3D2 face=3DArial><span
> style=3D'font-size:10.0pt;font-
family:Arial'>ADO</span></font></st1:place
> ></st1:City><font
> size=3D2 face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>. Should I
> go back to DAO to do this?<span style=3D'mso-spacerun:yes'>
> </span><o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-
family:Arial'><o:p> </o:p></span></fo
> nt></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>Microsoft may argue that
> the DataSet
> can be saved as XML and therefore the dataset representation is not
> needed. The
> counter argument is that the XML can’t be the operated on with SQL
> statements. Microsoft may then argue that an XML file can be operated on
> for
> the same results, but with different
> techniques.<o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-
family:Arial'><o:p> </o:p></span></fo
> nt></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>Help or comments,
> anyone?<o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-
family:Arial'><o:p> </o:p></span></fo
> nt></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-family:Arial'>Gary
> Minor<o:p></o:p></span></font></p>
>
> <p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D2
> face=3DArial><span
> style=3D'font-size:10.0pt;font-
family:Arial'>Controlware<o:p></o:p></span
> ></font></p>
>
> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
> style=3D'font-size:
> 12.0pt'><o:p> </o:p></span></font></p>
>
> <p class=3DMsoNormal><font size=3D2 face=3DArial><span
> style=3D'font-size:10.0pt;
> font-family:Arial'><o:p> </o:p></span></font></p>
>
> </div>
>
> </body>
>
> </html>
>
> ------=_NextPart_000_0005_01C1A467.18BF9500--
>
|
|
|
View Cart
