putting a database on the internet

[Paluccie]

I currently have a database in Access 2002 with multiple forms, tables, queries, name it I probably have it. In this database I store customer information, workorders, orders invoices everything. I would like to put this online so that my partner and I can use it and not have to email the database back and forth. Its becoming a pain. So if anyone has any ideas as to how I would do this, please let me know thanks.

[vass0922]

Do you want to just put the DB file online or do you want to make a webpage to access the information?
Don't forget you're putting customer information on the net regardless and thats not something youjust want to throw up on the net real quick.. it is people's privacy you're putting at risk. If you're gonna do it, do it right

[Paluccie]

I'm basically trying to use the database online as if i was to use it in access. I'm just trying to see how this is going to work before I worry about encrypting everything and whatnot. So i guess to answer your question its a web page, but the problem is is that i'm not just using 1 table and form is multiple tables and forms... for instance i have a customers workorder page then a page for workorders, one for payments and what not but they are all linked. Everything works fine in access now just trying to get it online

[vass0922]

quick and dirty way would be to plug in (blech) MS front page, it'll give you quick and easy access to your data w/o having to worry about the code too much. I think Access can make html forms, but they're pretty cheesy I believe. So it maybe an option

If you wanted it cleaner for customer purposes you could learn some asp or some other scripting language to access the data and generate a webpage with a given set of data.

[Paluccie]

alrighty i'll try that thanks

[qball]

access.net? access#?

lol,lol. That's one degree of separation....

joking aside, did you ask microsoft, since you pay $$ for their sw?

start with them, as they make access. see what solutions they offer?

you'll find none of them, complete, easy, simple, cost effective, or very web friendly.

Now to your problem described in original post.

Putting the DB online will not solve your problem, though it will lead to other issues, you may/maynot want to deal with...

Try this:

Instead of emailing ?.mdb back and forth, learn how to use access, so everyone uses same ?.mdb.

As in only one exists. you, partner, whomever, use same file. This would include the concept of networking, which you use by email. That way concurrency goes out window.

Now, the problem you have is you use access for DB and for interface (forms). This will not work well in an environment outside of access.

To put access DB on www:

vas0922 is giving good advice.

One can use accessDB with fp AND webserver that understands fp extensions. Meaning, using fp, and uploading, to said web server, one can actually get to DB data.

What about the forms? The interface you use. May/maynot work. fp/access may be able to HTML certain access forms to usable over www.

The whynot is simple. One can do things in a client/server environment (the way you use access), that are not possible over www.

Simple example:
access. Have form where user chooses customer from dropdown. Upon choice, the other form fields populate with appropriate info. This is client/server, and you maintain a persistent connection to access.

www. NO persistent connections exist. Therefore, you can display a page with customer dropdown, but upon user choice of a given customer, some things can happen:

nothing. oops!

choosing a customer from dropdown will link back to retrieve the appropriate info. may be good enough. notice, link back.

you cached all the customer info into display page with customer dropdown and client side (browser) scripting will update other fields upon choice. this is normally bandwidth intensive and well, basically stupid.

Simple. If I can only get my posty notes to play fair...