The information will be in the table, because
the form in Access is connected to the table.
It is an access problem, where I do not want
users to access the database, but instead use
an external form. Then take the info from the
external form and put it in the database.
You have told me, again, how you want to do something, but not exactly what
you want to do, and what the purpose would be for doing what you want. It is
entirely possible that someone could offer a suggestion to accomplish your
purpose that is simpler and easier than your proposed solution -- if only we
knew what your purpose _is_.
Let me ask , one more time: "Help me understand-- why do you want to put the
data into an Access form from the external Form, rather than storing it
directly into the Access table from the external Form? Sorry I am so dense,
but it is not obvious to me what you are trying to accomplish."
What do you expect to gain by using an external Form for data entry? What
is it that you are trying to protect? You seem perfectly happy to allow
users to add Records to your Database via an external Form.
But, for using the external Form, the answer is you will use Data Access
Objects or ActiveX Data Objects code in Visual Basic for Applications in
either Excel or Word to write the data entered into the external Form by the
user into the Table in the Access/Jet Database. You could do something
similar with a second Access database containing the entry Form with
restrictions on the functionality that Form allowed, linked to the actual
Tables in the database you want to protect.
To insert the data from an MS Form in Excel or Word into an Access Form,
you'd use COM Automation to control Access from Excel or Word. That's one
to Google, or to get and study an advanced self-study book such as "Access
Developer's Handbook" by Litwin, Getz, et al, from Sybex for the version of
Access you are using.
I don't do VBA in Excel or Word... the VBA itself is the same, but the
Object Model is very different between Databases, Spreadsheets, and Word
Processors... nor do I use MS Forms with Access (and would view with some
alarm anyone so rash as to do so), so I'm not a good person to advise on the
details of the approach you seem determined to use.
Larry Linson
Microsoft Access MVP