通过电子邮件在数据库之间传输访问记录 [英] Transfering access records between databases via email?
问题描述
大家好，
我相对刚刚访问和VBA等。我的表格和表等等
工作得很好并且节省了很多时间......但是...
我有两个数据库具有完全相同的表格格式。我希望db1是用来输入远程操作员数据的
，当她准备就绪时我想要她
能够点击控制按钮给她的新数据发送电子邮件到db2。这个
的新数据将被添加到db2中的表格中，以便进一步处理
。
这基本上是一个电话营销数据库db1的用户输入销售线索的联系方式，然后将这些信息发送到db2，其中用户跟踪这些线索并处理数据。我希望尽可能多的自动化，特别是在第一个实例（db1）中。
任何帮助都会很棒！如果需要
，请询问更多具体细节......（这也很难描述我想要的东西!!）
谢谢你
Walshi UK
它只是来自一个表的数据吗？那么为什么不直接导出为csv文件
文件...你可以在另一端轻松导入该文件。
此外，你还只生成一个带有新记录的mdb文件，并且
该人发送电子邮件.....
如果数据涉及多个数据表，那么你或者每个表格都有一个单独的csv文本文件，或者
只需通过电子邮件发送带有数据的mdb（即你的export / email例程
使得。
，你甚至可以考虑使用xml进行数据导出/导入，因为
允许你轻松通过电子邮件发送代表复杂数据的单个记录
结构（这更需要通过电子邮件发送一条
信息，这些信息将由多于一个表示表）。
如果对方偶尔会*连接到您的网络，那么
复制也可能是一个考虑因素。 （例如：旅行销售人员在路上......当他们回到办公室时，他们会*复制他们的
数据。（这假设您的用户将与
* *办公室网络连接良好
-
Albert D. Kallal（访问MVP） ）
加拿大艾伯塔省埃德蒙顿
pl * ****************@msn.com
" Albert D. Kallal"< Pl * ******************@msn.com写在
新闻：QsJ9h.363900
5R2.160610 @ pd7urf3no：
如果另一个人偶尔会*连接到你的
网络，那么复制也可能是一个考虑因素。（例如：
旅行中的销售人员......当他们回到
办公室时，他们*复制*
你的意思是同步他们的数据。
他们的
数据。 （这假设您的用户将有一个良好的连接
到*相同的*办公室网络）
最简单的复制形式可靠地工作通过局域网
连接，如果您的远程用户进入办公室，那么这是一种非常适合同步的方式。但是，复杂性是Access中提供的
UI不处理前端/后端，因此你需要打开后端才能进行同步（没有情况
你的应用程序不应该拆分，而且在复制方面，
它更为重要，因为前端对象不能可靠
复制）。
如果你没有可靠的高速连接到局域网
（即不是无线，至少10Mbps），然后有其他
形式的复制。但是那些设置起来比较复杂，并且需要维护和依赖Access本身以外的组件（尽管它可以编程为独立的
）。
-
David W. Fenton http ：//www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Hi all,
I''m a relative newby to access and VBA etc. My forms and tables etc are
working great and saving lots of time...However...
I have two databases with the exact same table format. I want db1 to be
used to input data by a remote operator, when she is ready I want her
to be able to click a control button to email her new data to db2. This
new data will be added to the table in db2 ready for further
processing.
This is basically a telemarketing database where the user of db1 enters
the contact details for sales leads, these are then sent to db2 where
the user follows up on these leads and processes the data. I want as
much automation as possible, particularly in the first instance (db1).
Any help at all would be great! Please ask for more specific details if
needed...(It''s just as hard describing what I want!!)
Thank you
Walshi UK
Is it just data from one table? Then why not just export as a csv text
file...you can easily import that file on the other end.
Further, you also just generate a mdb file with the new records, and have
the person email that.....
If the data involves multiple tables of data, then you either
email a separate csv text file for each table, or
just email a mdb with the data (that your "export/email" routines
makes).
and, you could even consider using xml for the data export/import, as that
allows you to easily email a single record that represents a complex data
structure (this would be more orientated to need to email ONE piece of
information that is to be represented by more then one table).
If the other person would have *occasional* connection to YOUR network, then
replication could also be a consideration. (eg: traveling sales people on
the road..and when they come back to the office, then they *replicate* their
data. (this assumet that your users will have a good connection to the
*same* office network)
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
"Albert D. Kallal" <Pl*******************@msn.comwrote in
news:QsJ9h.363900
5R2.160610@pd7urf3no:
If the other person would have *occasional* connection to YOUR
network, then replication could also be a consideration. (eg:
traveling sales people on the road..and when they come back to the
office, then they *replicate*You mean "synchhronize" their data.
their
data. (this assumet that your users will have a good connection
to the *same* office network)The simplest form of replication works reliably over a LAN
connection, and if your remote users come into the office, is a
perfectly suitable way to synch. However, the complexity is that the
UI provided in Access does not deal with front end/back end, so you
have to open the back end to do your synch (there is no situation
where your app should not be split, and in terms of replication,
it''s even more essential, as front end objects cannot be reliably
replicated).
If you don''t have that reliable high-speed connection to the LAN
(i.e., not wireless, and at least 10Mbps), then there are other
forms of replication. But those are more complicated to set up and
maintain and depend on components outside Access itself (though it
can be programmed to be self-contained).
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
这篇关于通过电子邮件在数据库之间传输访问记录的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
