Database and WANs

  • Thread starter Thread starter QB
  • Start date Start date
Q

QB

I know a standard access db should not be used over a WAN.

That said, is there a way. Can one be setup using adodb or some other
method that instead of keeping a constant link would do a form of transaction
back and forth. Please forgive the terminology (I am not sure how to put it
- it is more the concept I hope you can follow).

I love the access forms, reports, ... and was simply wondering if there was
a way to keeping working with it. I know I have seen people talk about Jet
rather than Access, and I still am unclear of the difference. One way or
another, is Jet a solution in this case?

Thank you for your advice,

QB
 
On Tue, 10 Nov 2009 19:27:53 -0800, QB <[email protected]>
wrote:

Jet is the database engine used by Access by default.

If you want to exchange data over a less-than-perfect link, you want
to use a mechanism that does not rely on this link to always be there.
For example you could use unbound forms, and in the Form_Open event
query for the data to be displayed, and do this in a way integrated
with the error handler so that you will retry a few times if the call
initially did not succeed.

Web pages are inherently stateless and work well over a WAN such as
the internet. This would require a different skill set, unless you are
in an intranet environment with SharePoint and could use the
forthcoming Access 2010.

If the app is only used casually and an occasional error message or
crash is not disastrous, the normal linked tables (e.g. to a SQL
Server exposed by an ISP) will work most of the time.

A terminal server solution where the user is actually running a
session on a central server is another strong option.

-Tom.
Microsoft Access MVP
 
Back
Top