Big Project Question

[KarmaPolice]

Well...I started writting out what I wanted to do and realized that its so complicated to explain that I doubt anyone is going to read through it all. I am going to try and break it down in a simple start off question.

What are some ways to have users enter data into an Access database? I would prefer to use only Access and Excel. The users would need to be able to look up multiple records using a query I suppose, and then be able to edit the data. The only way I know how to do this now is to actually use Access and I wouldn't want everyone just messing around in access.


I really need to have a dialouge with someone to explain what I am trying to do and actually get some help...but I don't know anyone who knows database sytems well at all.

Anyone up for some IM/Yahoo/MSN/Gmail?

Oh yeah first post...

 

[rainman89]

you can make it so that they cant "mess around" and have only the option to access certain forms and data using access security and other ways.

 

[twoplustwo]

"enter data into an Access database"

A form???

I mean, this is a pretty broad question.

 

[neileg]

Just to summarise/expand on the answers you already have.

A well designed application does not allow users to see queries or tables; they enter, change or view data using forms and view data in reports. As rainman suggests you can make it difficult or impossible for users to get at the underlying data with a few different approaches.

 

[ListO]

Hey, Karma

I apologize if I mis-read you here, but it sounds as if you're a beginner with Access, so: Welcome to Access. You are indeed asking a very broad question, so you will probably only get puzzled or broad answers. But you've got to start somewhere.

My answer to your question would be: You have to design a database, and then design an application 'Front-End' which will access and manipulate the data in that database. If you expect other users on a network to share the data and have them altering the data, you must design this Front-End application so that it allows some actions and prohibits other actions from those users so that the database doesn't get all fouled up. It's a big task. But like all big tasks, you have to break it down into smaller bits, work them out, and get it online.

I am an amateur programmer. I began building a database application which I use for my real profession. It took me about 8 months to get it built up well enough to use at all, and I'm now in my eighth year of modifications and improvements and bug-fixing. So unless you're an incredible programming genius, expect that it will take quite a lot of time, effort, thinking, re-thinking, trial, error, error, error, and (if you learn enough) success.

Good luck.

-Curt