>-----Original Message-----
>This is a newcomer's question (So far, I have produced
>only small applications to run on computers within my
>reach, using text files instead of "real" databases.)
>
>What I want to do:
>Create a self-contained Windows Application;
>Allow the user to create a database;
>Allow the user to store and update this database.
>The user database should run only from within this
>distributed application.
>
>The questions:
>Can I use ADO components to accomplish this (I know how
>to create front ends to my own Access program)? While I
>tried to connect to a text file database, the following
>questions occurred to me:
>
>How do I make sure a user/customer has all the
components
>to safely connect to the DataSource? The users I know
>will refuse to use the Administrator's Tools even if
they
>knew where to find them.
>
>Looking at the schema.ini file I wondered what would
>happen after the user has put in a lot of data and runs
>out of memory?
>
>What is the best setup for a self-contained program when
>I do not know what software the user has (certainly not
>SQL Server)?
>
>I know I have to supply MDAC 2.7 or higher, are all
other
>support files included?
>
>My tools: VS.Net Enterprise ed. 2002, SQLServer, v.8,
>Dev.Ed.
>(lots of tools, little experience)
>
>I do not expect you to tell me exactly how to write the
>program. I would appreciate a hint to get me started
>using the proper tools and the components that are the
>easiest and most robust to use. Already, I bought plenty
>of literature and spent days on the Internet. Are there
>any books or examples that could help me to get started
>(the MS samples are too complex and therefore useless to
>answer basic questions. Most examples mix the most
>intricate information from 3 or 4 different areas).
>
>I would not just appreciate any pointers to real down-to-
>earth information for a newcomer to dotnet, I would be
>outright grateful.
>
>Thank you so much,
>
>Ursula
>
>
>.