Sending a form by email?

  • Thread starter Thread starter jb
  • Start date Start date
J

jb

Hi.
Is there a way of sending just one aspect of a database from access as an
attachment?

I've re- designed a form for a friend for her database.
I had a copy the database on my pc from a month ago. Since then she has
increased her records and data. So I can't send her the whole database as
her records are more recent and I don't want the one I send to override
hers.
How can I send her this particular form?
When I do export it doesn't allow me to do it. Well maybe I'm doing
something wrong.
Or if I sent her the whole thing would it merge with the data (forms queries
and reports ) that she has?
Thanks
 
jb said:
Hi.
Is there a way of sending just one aspect of a database from access as an
attachment?

I've re- designed a form for a friend for her database.
I had a copy the database on my pc from a month ago. Since then she has
increased her records and data. So I can't send her the whole database as her
records are more recent and I don't want the one I send to override hers.
How can I send her this particular form?
When I do export it doesn't allow me to do it. Well maybe I'm doing something
wrong.
Or if I sent her the whole thing would it merge with the data (forms queries
and reports ) that she has?
Thanks
Click to expand...

An Access object cannot really exist outside of an MDB. You could use two
undocumented commands, SaveAsText and LoadFromText to send it to her as a Text
file.

You would use SaveAsText to create the Text file and she would use LoadFromText
from within her MDB to bring the object into her MDB.
 
Thanks Rick , I'll give that a go.
J

Rick Brandt said:
An Access object cannot really exist outside of an MDB. You could use two
undocumented commands, SaveAsText and LoadFromText to send it to her as a
Text file.

You would use SaveAsText to create the Text file and she would use
LoadFromText from within her MDB to bring the object into her MDB.
Click to expand...
 
Rick's given you a good approach for your current problem. For the future,
though, you might want to split the application into a front-end (containing
the queries, forms, reports, macros and modules) and a back-end (containing
just the tables).

Then, all you'll have to do is supply a new front-end (and a method of
linking the new front-end to the existing back-end)
 
God I wish I knew what that all meant!
Thanks so much for your time but I got lost with front-end and
back-end.

J
 
Back
Top