Can I have a backend database on the internet?

[AccessGuruCarl]

Hello All,

I have a database I want to split into frontend/backend.

I want to have the backend database at a website like:

http://www.yoursite.com\client\dbs

The frontend database has a client table and a login table(linked to backend)
The user adds a client, and issues a login for them which is stored in the backend, so that when the client needs to access the database it checks for a correct login before allowing user into other tables.

Is this possible?

AccessGuruCarl
Programmers helping programmers
you can't find a better site.

 

[fneily]

You'll get different responses from the ASP people out there, but if you create Data Access Pages(DAP's)(the Page object in the database window), you're actually creating web pages (extension .htm). These reside OUTSIDE of Access. As long as your tables are on the web server with you're DAP's, you're users can access the data. You would create a login web page.
In your post it sounds like the client and login table are on the local computers. If this is right, why aren't they on the backend with the rest of the tables?

 

[AccessGuruCarl]

Hi fneily,

Thanks for the post...

The reason for the login's being in the backend and the client info in the frontend was we didn't want the entire client info on the web. Incase someone got ahold of the database. I used DAP once, and didn't care for the results, I'd use .asp if I need the user to enter a new client. But I hoping I could link it to a network location as stated below.

Can I use the network wizard to add the web folder(off-site location) as a network location, map it to a drive letter, then use the linked table manager to link the backend. I do this at home, but at home I also host the website so I'm not sure if this can be done with an offsite location.

I don't work directly for this company but Presently, I'm having their IT group network this for other uses. But I was hoping someone has already tried this method!

Thanks Again...



AccessGuruCarl
Programmers helping programmers
you can't find a better site.

 

[RuralGuy]

Since the internet is *soooo* much slower than a LAN, I don't think you will be satisfied with the results unless you use Citrix or something like it.

HTH RuralGuy (RG for short) acXP winXP Pro
Please respond to this forum so all may benefit

 

[BNPMike]

It's not easy using Access on the Internet because Jet is a client-managed database. True, Data Access Pages can make Jet work but you're probably going to have to give too much access to people so that you won't be able to satisy normal web security/firewall standards.

 

[fneily]

AccessGuruCarl- Have you looked at Citrix (

http://www.citrix.com)?

Not much developement time involved.
BNPMike- so since DAP's utilize ASP, XML, etc., they too don't meet "security/firewall standards."?

 

[AccessGuruCarl]

Thanks for the posts guys,

Haven't looked at Citrix, I'll have to take a look.

Speed isn't an issue. The front-end user doesn't add that much data, and new records would occur very seldom.

Just looking for a quick solution for them to maintain web users.

I have an appointment scheduled for tommarrow, to test this on their network.

I'll post my results, and let everyone know if this can be done.



AccessGuruCarl
Programmers helping programmers
you can't find a better site.

 

[BNPMike]

since DAP's utilize ASP, XML, etc., they too don't meet "security/firewall standards."? "

When I last looked DAPs use an ActiveX control so no ASP and no XML. The ActiveX control has to fetch data like an ordinary Access form, so it needs wider privileges than your normal HTML set-up.