I have an Access database on a local server that I would like to
remove and put on the internet so I can share it remotely between at
least 2 people. We both may be updating and reading from this
database. It is about 5 mb in size. What is the easiest way to share
this database using the internet?

* Is there a file storage location that we could both access like it
was a disk drive that would have locking/sharing capability?

* Could I make a drive directory on a machine I have be common to
both of us over the internet? How would that be done? Would it be
too slow for use as an Access database?

* Would it just be better to upload the database from a backup
location on the Internet and download the update after records are
updated?

In my option, using a Windows Server with indiviual access through Remote
Desktop connections is the easies, quickest and maybe the safest way to go.
I currently run a database in which we have over 100 clients accessing
through RDPs (they RDP automatically appears through a weblink on our
internet site).

Maintence can be done all on one server without the need to mail out new
front ends to each user. Instead, I maintain a folder of frontends unique to
each individual users RDP login. Updating all 100+ RDPs when necessary is a
snap.

And finally, you don't have to deal with converting your nice Access forms
into web pages which can be a royal pain if you are note HTML savvy.

B

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200707/1

B -

I run the same scenario as you do, but I'm interested in how you do your
frontend updates....can you share?

Jeff G

"bhipwell via AccessMonster.com" <u30281@uwe> wrote in message
news:75504857f1ad9@uwe...
> In my option, using a Windows Server with indiviual access through Remote
> Desktop connections is the easies, quickest and maybe the safest way to
> go.
> I currently run a database in which we have over 100 clients accessing
> through RDPs (they RDP automatically appears through a weblink on our
> internet site).
>
> Maintence can be done all on one server without the need to mail out new
> front ends to each user. Instead, I maintain a folder of frontends unique
> to
> each individual users RDP login. Updating all 100+ RDPs when necessary is
> a
> snap.
>
> And finally, you don't have to deal with converting your nice Access forms
> into web pages which can be a royal pain if you are note HTML savvy.
>
> B
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/For...ccess/200707/1
>

Basically I have a folder on the server named "Front Ends" that has as many
unique front end databases as I may need. The RDP for each user
automatically starts Access and the subsequent file specific to that client.

To update, it really is as simple as making the initial replica, copying as
many times as you need and the renaming each front end database to the
cooresponding RDP user.

B

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200707/1

Let me play stupid.....how do you do that with the unique RDP users?

"bhipwell via AccessMonster.com" <u30281@uwe> wrote in message
news:7551aabeb1110@uwe...
> Basically I have a folder on the server named "Front Ends" that has as
> many
> unique front end databases as I may need. The RDP for each user
> automatically starts Access and the subsequent file specific to that
> client.
>
> To update, it really is as simple as making the initial replica, copying
> as
> many times as you need and the renaming each front end database to the
> cooresponding RDP user.
>
> B
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/For...ccess/200707/1
>

Not sure if I understand your question.

Under the Environments tab of your RDP users properties, there is a Starting
Program option. That option would read:

"c:\program files\microsoft office\office\msaccess.exe" "c:\
yourfrontendfolder\user1.mdb"

B

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200707/1