Data access web page

[Clintimania]

This is my first attempt using a web page to work with access. Here is the setup.

I have created a work order system in access that works great on network. However, we have some users that connect remotely through a portal that cannot use the access version. (their use computers provided by another business, so that do not have our drive mappings AND some do not have Microsoft Office) When they connect through the portal, the portal gives them a on-network connection. So I created a data access page and made all the connections work using \\server\share\file setup. It is working, but I have a couple of obstacles that I do not know how to get around...

1. When you open the data access page, it gives you two messages asking if you trust the website... how do you turn these off?

2. The connection is really slow. After you select ok on these two messages, it takes 3-4 minutes for the page to become active. It also takes 2-3 minutes to save a record.

3. In my on-network version, when they create a work order, it sends emails out to people, any idea how to do that on the web based?

4. I would like to display a message saying "Record Saved" after they click the save button.

I know this is a lot, if there is a site I should study or something, I would welcome a link.. or any help at all.

Thanks

 

[Simon_MT]

How many remote users do you have and users in total.

Simon

 

[Clintimania]

120 local users... only about 18-20 remote. It is going to be a work order system, so they will only use it to report I.T. problems... I dont forsee a lot of traffic.

One note from the first post, I was connecting to it remotely using a Sprint Air Card... I had low signal on it, so that could be some of the 3-4 minute slowness. Not all I do not think, but some.

 

[ghudson]

One note from the first post, I was connecting to it remotely using a Sprint Air Card... I had low signal on it, so that could be some of the 3-4 minute slowness. Not all I do not think, but some.

Wirelessly connecting to an Access database is not recommended. Access databases can be corrupted when unintentionally disconnected.

 

[Clintimania]

I agree, our remote users will not be wireless... I only used it to test a few things. It was the only not-on-network connection I had available.
Thanks for the tip though.

 

[Simon_MT]

I would suggest that a Terminal Server is considered. Basically, remote users log into the Terminal Server, have a Front end each on the Terminal Server. All the calls are local to a file server. The Terminal Server will essentially just past the screen dumps over the internet.

It is set-up correctly it will run efficiently.

Remote users can use wireless providing they use the Terminal Server providing there is a grace period before ending each session. I have known some users hot swap remote PC and resume their session on another PC.

Simon