在笔记本电脑上访问数据 [英] Access Database on Laptops
问题描述
我创建了一个客户联系人数据库，供我的笔记本电脑上的远程销售人员（10-15人）使用。
我想帮助决定如何让这些用户保持最新状态。
远程用户遍布全国各地，并且将以不同的时间间隔访问他们的区域办事处 - 然后他们将可以访问局域网中的信息可以更新。
我预计每个用户只会更新自己客户的记录。
我期待我将数据库的前端分割成数据，然后需要同步。远程用户具有不同的计算技能，因此可能无法更新前端 - 我是否可以保护前端以阻止他们进行更改。
系统应保持简单可能为远程用户。
我正在使用Access 2003.
我的网络经验很少。
< blockquote class =post_quotes>
- 我可以保护前端以阻止他们进行更改。
保护前端不是问题，因为你可以创建一个mde。
创建一个前端的mde以下内容：
创建mdb文件的主备份，因为您无法更改即将创建的文件。
1.创建filename.mdb的备份副本前端
2.转到工具 - 启动并将启动表单设置为您创建的交换机/菜单表单。取消选中显示数据库窗口。如果您已创建自定义菜单，请将菜单栏更改为自定义菜单，然后取消选中允许完整菜单。和允许工具栏/菜单更改框。请注意，如果您的任何用户都是有经验的用户，他们可能会想方设法解决此问题。这需要经验丰富的开发人员或一些时间来完整地解释和编码。
3.转到工具 - 数据库实用程序 - 制作mde文件。这将创建该文件的可执行版本，并且您或其他任何人不能在结构上对其进行更改。
我想帮助决定如何让这些用户保持最新状态。
远程用户是遍布全国各地，并且将以不同的间隔访问他们的地区办事处 - 然后他们将可以访问可以更新信息的LAN。
我预计每个用户只会更新自己客户的记录。
这部分有点困难。
每个前端都有自己的临时后端，这是需要更新的内容。这些需要在每台笔记本电脑上进行链接，因此需要在前端提供链接表管理器工具才能实现这一点。
第一个问题是用户是否会更新任何记录或以任何方式更改数据，因为这需要双向同步。
如果他们每个人都需要一组特定的数据（即他们自己的客户记录，那么这将需要一些适合每个前端的复杂VBA代码来专门更新他们的记录）。更新所有记录会更容易，只允许他们根据登录数据访问自己的客户。
如果没有双向同步并且所有记录都在更新，那么他们会只需要从局域网中复制后端并在自己的笔记本电脑上替换后端。
Mary
谢谢Mary
我希望我的用户能够查看（和编辑）所有记录，但我希望主要是对他们自己的客户进行编辑。
我需要吗？在同一时间表上同步所有副本，因为用户可以在不同时间访问LAN。他们可以按照自己的时间表更新后端副本。
谢谢Mary
我我希望我的用户能够查看（和编辑）所有记录，但我希望主要是对他们自己的客户进行编辑。
我是否需要同步所有副本用户可以在不同时间访问LAN的计划相同。他们可以按照自己的时间表更新后端副本。
如果用户更新他们的记录，你会遇到更复杂的情况。标准同步不会双向工作。您将需要一位经验丰富的VBA程序员，他们可以制定一套程序来验证两个方向的数据更新。这是一个复杂的问题，我建议聘请专家处理。
Mary
I have created a database of customer contacts for use my a team of remote sales staff (10 -15 people) on their laptops.
I would like assistance in deciding how to keep these users upto date.
The remote users are based all over the country and will all be visiting their regional office at varying intervals - they will then have access to a LAN where the information could be updated.
I would anticipate that each user would be updating only their own customer''s records.
I anticipate that I shall split the front end of the database form the data which would then require to be syncronised. The remote users have varied computing skills and therefore will probably not be updating the front end - can I secure the front end to stop them making changes.
The system should be kept as simple as possible for the remote users.
I am using Access 2003.
I have minimal network experience.
- can I secure the front end to stop them making changes.Securing the frontend is not a problem as you can create an mde.
To create an mde of the frontend do the following:
Create a master backup of the mdb file as you won''t be able to alter the file about to be created.
1. Create a backup copy of your "filename.mdb" frontend
2. Go to Tools - Startup and set the startup form to the switchboard/menu form you''ve created. Uncheck the "Display Database Window". If you have created a custom menu then change menubar to the custom menu and uncheck the "Allow Full Menus" and "Allow Toolbar/Menu Changes" boxes. Please note that if any of your users are experienced users they may find ways around this. It would require an experienced developer or some time to explain and code them out fully.
3. Go to Tools - Database Utilities - Make mde file. This will create an executable version of the file and this cannot be altered structurally by you or anyone else.
I would like assistance in deciding how to keep these users upto date.
The remote users are based all over the country and will all be visiting their regional office at varying intervals - they will then have access to a LAN where the information could be updated.
I would anticipate that each user would be updating only their own customer''s records.This part is a little more difficult.
Each of the frontends would have their own temporary backends which is what would need to be updated. These would need to be linked on each laptop and therefore the linked table manager tool would need to be available in the frontend to allow for this.
The first problem is whether the users would be updating any records or in any way changing the data as this would require a two way synchronisation.
If they each needed a specific set of data (i.e. their own customer records then this would require some complicated VBA code adapted for each frontend to specifically update only their records). It would be easier to update all records and only allow them access to their own customers based on login data.
If there is no two way synchronisation and all records are being updated then they would only have to copy the backend from the lan and replace the backend on their own laptop.
Mary
Thanks Mary
I would prefer my users to be able to view (and edit) all the records, however I would expect mainly edits to their own customers.
Do I need to synchronise all the replicas on the same schedule as the users will have access to the LAN at different times. Can they update their back end replicas on their own schedule.
Thanks Mary
I would prefer my users to be able to view (and edit) all the records, however I would expect mainly edits to their own customers.
Do I need to synchronise all the replicas on the same schedule as the users will have access to the LAN at different times. Can they update their back end replicas on their own schedule.If users are updating their records you have an even more complicated situation. A standard synchronise won''t work both ways. You will need a very experienced VBA programmer who can draw up a set of procedures to validate the data update in both directions. This is a complicated issue and I would advise employing an expert to deal with it.
Mary
这篇关于在笔记本电脑上访问数据的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
