There are several tasks that I am attempting to accomplish.

1. I am wanting to use VBScript with ADO to read a fixed-length text file
containing 2 text (character)fields  using the  Access97 TEXT provider?

2. After reading each record from the text file I will do some record
manipulation with this text  record and then write this modified record to
an Access97  .mdb database.

3. I understand at this point I need to use ADOX to create an empty .mdb
database.  I have a code sample for this, but I do not know how to create a
table, or to create the fields  with specific field types. The table will
only have 3 fields, 2 of which are text(character) fields that have been
read from the text file above, with the 3rd field being generated by
vbscript (depending on the value of one of the text file fields). This 3rd
field will be a hyperlink field type.

So I guess I'm asking for either code snippets or boilerplate code that
would allow me to accomplish the above 3rd step.

I have seen numerous examples of ASP server-side code, but can find no
examples for Client-side VbScript local machine processing. I also have had
a very difficult time finding any VBScript coding examples. What confuses me
is that in the few vbscript code examples I have seen, they all seem to be
using different techniques to basically do the same thing.

If anybody can provide me with any examples, idea,websites,etc which will
help me accomplish the above I will be very appreciative. TIA

If there are any regular readers of this newsgroup who are interested in
ADO/VBScript/Access97 programming who might like to get together via chat or
email , that would be great too.

One suggestion that I have for you is to s{*filter*}using the TEXT driver for #1.
Try using the FileSystemObject, ReadLine and various text functions to parse
the file and fields.  You'll be much better off and it's quite fast to do
that.

For #2, there are various ways to do that.  Use the ADO methods or just
issue dynamically built SQL strings.  that's up to you.

#3.  If you are intent on learning ADOX (not a bad thing to be intent on),
then you *need* the DASDK 2.1 update.  Run, don't walk, to
www.microsoft.com/data and get the 2.1 update.  There is another CHM help
file in the update that contains good documentation on ADOX.   I've just
started looking at it myself to perhaps automate the installation of a data
syncing application that I've written.  There are pretty good samples in
this help file.

Good Luck,
John Alderson
Systems Analyst
Goodwin, Procter & Hoar LLP