I have a spreadsheet that I only want to use for user input. The user will
fill out a UserForm and then when the click a button, I want the information
they entered to be put into a worksheet (Columns A through I) in the next
empty row.

Then another user will open the spreadsheet, fill out the form, and the data
they entered should be put into the next empty row of the spreadsheet, etc.

So, I pretty much want to populate a table via user input from a UserForm.
I would think this would be easy to figure out, but I can't. I have tried
creating a named range for the data and inserting, I have tried using the
cell names. I just need a little bit of guidance on how to do this and I
will be ready to go.

I am very new to Excel VBA as I am an Access guy and this sort of thing is
inherent in access apps. The major problem I have had is knowing where/how
to put the next row without overwriting any rows. I don't know how many
rows there will eventually be, but probably a lot.

Lydon D. Bergin
MCP, MOS

Hi Lydon

You can link textboxes to a cell in your worksheet (see properties) and then use code like this to copy the range in the database
sheet with this
http://www.rondebruin.nl/copy1.htm



--
Regards Ron de Bruin
http://www.rondebruin.nl


"Lydon Bergin" wrote in message ...
I have a spreadsheet that I only want to use for user input. The user will fill out a UserForm and then when the click a button, I
want the information they entered to be put into a worksheet (Columns A through I) in the next empty row.

Then another user will open the spreadsheet, fill out the form, and the data they entered should be put into the next empty row of
the spreadsheet, etc.

So, I pretty much want to populate a table via user input from a UserForm. I would think this would be easy to figure out, but I
can't. I have tried creating a named range for the data and inserting, I have tried using the cell names. I just need a little
bit of guidance on how to do this and I will be ready to go.

I am very new to Excel VBA as I am an Access guy and this sort of thing is inherent in access apps. The major problem I have had
is knowing where/how to put the next row without overwriting any rows. I don't know how many rows there will eventually be, but
probably a lot.

Lydon D. Bergin
MCP, MOS