How to Deploy MS Access Application so multiple offsite users can update simultaneously
I have a sales database which i've been developing that will track sales opportunities of our salesforce. The salesforce is obviously located in the field, and will rarely be in the main office. They will therefore be updating their data from home (likely on a nightly basis). I'm sure there will be many times when multiple salesmen will be trying to update at the same time. I'm trying to figure out what the best way to implement this is. I'm relatively new to Access and have not implement anything yet that needs updated by multiple people.
As far as remote access for the salesmen, they have two ways that they log on to our server. For email, they log on to Outlook Web Access. If they need access to our server or an office computer, we do that through Remote Web Workplace (SB Server 2003). They have never really had the occasion to do much more than the Outlook Web Access until now.
Any help on how to implement this would be appreciated. I guess the main thoughts/questions i have are as follows:
1. how do i properly account for the fact that multiple users may be trying to update or open the database at the same time?
2. Do i need to worry about users corrupting the form or database? is there anything i should do about that?
3. Also, i've read a little bit that Access 2007 (which i am using) has some sort of e-mail update capabilities. Not sure how robust this functionalitiy is and if it would work with a fairly complex input form that has multiple tabs and subforms. If this is a viable possibility for me, i'd like to know if its the best way to pursue.
Anything else that i haven't thought about yet or didn't mention?
As far as remote access for the salesmen, they have two ways that they log on to our server. For email, they log on to Outlook Web Access. If they need access to our server or an office computer, we do that through Remote Web Workplace (SB Server 2003). They have never really had the occasion to do much more than the Outlook Web Access until now.
Any help on how to implement this would be appreciated. I guess the main thoughts/questions i have are as follows:
1. how do i properly account for the fact that multiple users may be trying to update or open the database at the same time?
2. Do i need to worry about users corrupting the form or database? is there anything i should do about that?
3. Also, i've read a little bit that Access 2007 (which i am using) has some sort of e-mail update capabilities. Not sure how robust this functionalitiy is and if it would work with a fairly complex input form that has multiple tabs and subforms. If this is a viable possibility for me, i'd like to know if its the best way to pursue.
Anything else that i haven't thought about yet or didn't mention?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
LSM,
How difficult is it to move this to SQL Server Express.........or SQL Server (I know we have it)?
The Terminal Server may be an option.
I dont totally understand it as you described. I dont think its a problem if they wait to update all of their calls until they are at home or the hotel. If thats the case, how exactly would it work?
Would it simply be a local copy of the entire Access file, including all tables and forms etc, that is simply synched up somehow?
How difficult is it to move this to SQL Server Express.........or SQL Server (I know we have it)?
The Terminal Server may be an option.
I dont totally understand it as you described. I dont think its a problem if they wait to update all of their calls until they are at home or the hotel. If thats the case, how exactly would it work?
Would it simply be a local copy of the entire Access file, including all tables and forms etc, that is simply synched up somehow?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks LSM,
The description you give for Terminal Server sounds exactly like Remote web workplace. For Remote web workplace, i type in a web address to my server from any machine that has internet access. I then choose which of the office PC's i want to log in to. Once i log on, i see that particular office machines desktop from my remote location. Are they the same? If they are different, do you see a benefit to using one over the other?
The description you give for Terminal Server sounds exactly like Remote web workplace. For Remote web workplace, i type in a web address to my server from any machine that has internet access. I then choose which of the office PC's i want to log in to. Once i log on, i see that particular office machines desktop from my remote location. Are they the same? If they are different, do you see a benefit to using one over the other?
It is similar, but my understanding of Remote Web Workplace is that you can connect to a single machine on the network, and use THAT machine as if you were sitting in front of it. Terminal Server supplies you with a true "remote desktop" ... that is, TS is NOT tied to a specific network machine, and doesn't depend on other network resources to provide that desktop. With RWW, you must connect to a specific machine in order to see that machine's desktop ... TS doesn't have this limitation, and can serve up many concurrent users at the same time. RWW can connect ONE user to ONE network machine ... so if I use RWW to connect, and the local workstation I want to use is not on, I can't connect. With TS, I'd get my remote desktop as always, regardless of whether any other network resource was running.
If your OTR users all have a specific "local" office machine, then they can use RWW to connect each user to THAT machine. If they do NOT, and you are expecting them to share the same "local" office machine, then I suspect you'd have some complaints if UserA is logged in but UserB needs to log in as well (since RWW would deny the second user a login), but I suppose this would depend on the user volume and such ...
If your OTR users all have a specific "local" office machine, then they can use RWW to connect each user to THAT machine. If they do NOT, and you are expecting them to share the same "local" office machine, then I suspect you'd have some complaints if UserA is logged in but UserB needs to log in as well (since RWW would deny the second user a login), but I suppose this would depend on the user volume and such ...
ASKER
LSM,
Sounds like TS is what i want then.
With TS, would i still split the database like was discussed in previous posts?
For someone relatively new to Access, is TS hard to implement?
We have an external IT consultant that is available for things that i can't handle, but i'd rather avoid that expense if i can figure it out.
How can i learn exactly how to implemnt TS?
Sounds like TS is what i want then.
With TS, would i still split the database like was discussed in previous posts?
For someone relatively new to Access, is TS hard to implement?
We have an external IT consultant that is available for things that i can't handle, but i'd rather avoid that expense if i can figure it out.
How can i learn exactly how to implemnt TS?
ASKER
A few questions on your post:
>The database MUST have a fornt end/ back end spilt (i.e. back end its the tables only, front end - the rest)
Can you elaborate on what this means? How i do it?
>You need a batch file or simple Access appn that grabs a master copy of the front end and copies it to the local drive.
Again, kind of new to Access, so can you give me some more detail on this as well?