From: Rob Rob on
I have a db with 5 columns and i want my front end interface to be
able to insert a 6th column. i can do it on the front end but it doesn't
save to the db?
From: Dorian on
You must change table design in the back end.
-- Dorian
"Give someone a fish and they eat for a day; teach someone to fish and they
eat for a lifetime".


"Rob" wrote:

> I have a db with 5 columns and i want my front end interface to be
> able to insert a 6th column. i can do it on the front end but it doesn't
> save to the db?
From: KARL DEWEY on
Access is not like a spreadsheet where you can insert columns (in Access they
are called 'Fields') at any time. You have to modify the table structure.

How were you attempting to insert a 'field'? What were you viewing when you
tried?

--
Build a little, test a little.


"Rob" wrote:

> I have a db with 5 columns and i want my front end interface to be
> able to insert a 6th column. i can do it on the front end but it doesn't
> save to the db?
From: Jeff Boyce on
Rob

Are you saying that you want your USERS to be able to add a column (via the
front-end interface)? If so, other responders have already pointed out that
Access is not a spreadsheet.

If you (and your users) want to get the best out of Access'
relationally-oriented features/functions, you can't feed it 'sheet data.
Access is optimized for well-normalized data.

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"Rob" <Rob @discussions.microsoft.com> wrote in message
news:8658F270-9A03-4785-865F-315519E429B8(a)microsoft.com...
>I have a db with 5 columns and i want my front end interface to be
> able to insert a 6th column. i can do it on the front end but it doesn't
> save to the db?