web based db or replication?

[Guest]

Hi,

I need some advice. I won't bore you with too many details but I've been
asked to build a db that is to be used on three work sites. They want the
data to be up to date for all three since they will be working on common
items. I thought of making a master and distributing 2 replicas and updating
them on a daily basis (but I have many issues with this method). Then I
thought about a web based bd were I could administer the db for my location
and user any where in world could login (but I know nothing about creating
such a db but am more than willing to learn).

I would like any insight any of you can provide! Other ideas to solve my
current problem. Any websites of reference for developing web based db?!

Thanks in advance!!!! It really is appreciated.

Daniel P.

 

[Guest]

they all have access to a central server yeah? why not put the info into one
database file in a table (i'll call it "data.mdb" to make life easy), put the
forms and stuff into another file (i'll call it "forms.mdb"), and link the
table from data.mdb to forms.mdb, then distribute forms.mdb across the
different sites?

would that solve your problem or have i misinterpretted you?

 

[Guest]

I'm sorry Chris I didn't quite follow that. Could you run that by me again.

Thanks,

Daniel

 

[Guest]

I just clued in.... sorry about that!

I'm worried about latency issues. These sites are literally half way around
the world from one another. How can I address these types of concerns?

Daniel

 

[Guest]

After more digging, I have had to throw out the idea of the front-end
back-end through a central server because at least 1 of the sites does not
have access to our internal domain/servers. As such, I am back to my
original question.

Thanks for the idea... I thought it was going to work. To bad it couldn't..

Daniel

 

[Guest]

Chris, my apologies. My question is posted in Security board.

 

[Guest]

Chris, can you read my question "Best way to share". Sounds like maybe this
would work for me. Thanks!

 

[SirPoonga]

microsoft.public.access.multiuser might be a good place to start
looking.

If they all have web access and you can make a web based front end,
doesn't that mean they all have access to a central server (ie the web
server)) that oyu could put the back end on? Probably not a secure
method though.

I have been learning ASP.NET. Super easy to make online forms if you
know VBA. Very simular if you use VB.NET syntax in your ASP.NET pages.
http://www.asp.net is the place to start for that.

Otherwise you can use the Pages tab in access to create pages but that
uses ActiveX. I frown upon ActiveX and all it's problems (and the fact
I use Mozilla so I can't use those pages).

 

[SirPoonga]

microsoft.public.access.multiuser might be a good place to start
looking.

If they all have web access and you can make a web based front end,
doesn't that mean they all have access to a central server (ie the web
server)) that oyu could put the back end on? Probably not a secure
method though.

I have been learning ASP.NET. Super easy to make online forms if you
know VBA. Very simular if you use VB.NET syntax in your ASP.NET pages.
http://www.asp.net is the place to start for that.

Otherwise you can use the Pages tab in access to create pages but that
uses ActiveX. I frown upon ActiveX and all it's problems (and the fact
I use Mozilla so I can't use those pages).