Access newb

[dsscripts]

Hi all,

I have very limited experience with Access and I am looking into setting up this scenario:

I want people to be able to fill out an excel spreadsheet template with information. The spreadsheet would be filled out differently per "project". I want the information on the different excels to be exporting to 1 Access file. The access and/or excel files can be stored on a Sharepoint site.



Does anyone have any recommended videos or tutorials I can follow to set this up? or am I in way over my head?

Thanks for your help.

[Xipooo]

I'd say you probably want to skip the whole "Excel" part and just make up a form in Access for people to enter the data.

[June7]

What 'people' are you talking about? Why does this need to be web delivered?

[dsscripts]

Thanks for both of your replies!

I'd say you probably want to skip the whole "Excel" part and just make up a form in Access for people to enter the data.

Unfortunately, this isn't really an option. We have to keep the original "forms" in excel format to be distributed, but then we want to compile all of the data in one location. I may have to consider keeping it all in excel if moving it over to Access is too difficult.

What 'people' are you talking about? Why does this need to be web delivered?

It doesn't have to be web delivered. I am just trying to find a way automate some of the data gathering/moving.

[June7]

A multi-user Access database should be split. The backend contains data tables and resides on central server. The frontend is the user interface (queries, forms, reports, code) and links to backend tables. The frontend should be distributed to each user.

[ssanfu]

I want the information on the different excels to be exporting to 1 Access file.

I haven't tried using automation to move data from Excel to Access. I have always used Access to import data from Excel.

For code to import from Excel to Access or export from Access to Excel, there is code at Ken Snell's site http://www.accessmvp.com/kdsnell/EXCEL_MainPage.htm

You say you want "1 Access file". If you mean 1 table, that might not be the best option. You need to have a normalized table structure which might result in many related tables.
If you really mean "1 Access file", as June said, you should have a split application.