Khalid-
By "live" data I mean all the active tables that contain data that is updated by the application. It is also possible to have local "working" tables that are not shared.
If you want to share for reporting only, create a version that has only the reporting functions it it and give that (or its .mde) to the users.
The purpose of an MDE file is to have a copy that you give to the users that contains none of your VBA code. The code gets "compiled" into an internal form to be able to run but which is not available to the user to see or edit.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Khalid Tanweer
Sent: Wednesday, November 06, 2013 9:19 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] Putting my Db on LAN
John,
I could not follow the term "live" data? What is the purpose of MDE then? and also how would i be able to restrict user's to not enter data in different forms. I only need that they have the access to view reports only.
Could you please also mark which one is said to be frontend?
PCTL
PCTL_be ( I assume is backend)
MDE
Khalid
On Wednesday, November 6, 2013 12:21 PM, John Viescas <JohnV@msn.com> wrote:
Khalid-
If there is no "live" data in your front end, then you should be able to give your app to anyone on the LAN that can connect to the back end machine. The back end machine doesn't need to be a server, but it should probably be dedicated to the task. As for multiple versions of Access, you'll have to test your 2003 front end to see if it runs OK in 2007. You should also add code to your front end to check the linked tables and offer a way to relink to a shared address. If you get past all those hurdles, then all you need is Bill Mosca's "front end updater" to ensure that users always have the current copy of the front end. Test changes on your machine, then put the new version on a share where users can get to it to download if an update is needed.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Khalid Tanweer
Sent: Wednesday, November 06, 2013 8:07 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Putting my Db on LAN
Hi John,
Since my database is giving almost all reports to my boss upto his current requirements and is satisfied.
Now he is demanding that he should be able to view reports on his Laptop. We have LAN but there is no Server at present. Also my boss is using Office 2007 and my database is in Access 2003. There is one more colleague who will also view reports.
At present i am myself developing and updating data in db.
I have my frontend, backend and MDE
My boss is keenly interested in this and is cooperative.
Can i manage this and how ?
One more question how long could i go with this db, i mean limitations of size, at present:
PCTL = 280 MB
PCTL_be = 12.8 MB
MDE = 267 MB
regards,
Khalid
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (4) |
Tidak ada komentar:
Posting Komentar