Disable insert of a new column before the 1st column

[Corcovadocowboy]

Hi everybody !

I link my Access database to another software and the link breaks, when
somebody inserts a new column before the first colmn. Is ther a possibility
to configre Acces in this fashion to block inserting a new column before the
first column or at least poping up a message?

Thanks in advance!

Corcovadocowboy

 

[boblarson]

My first question would be why in the world would people be adding columns to
your tables? This is not a good idea and, it makes it sound like you do not
have a properly normalized and designed database. It should be a RARE
occurance to add a field to a table. And, your users should not be anywhere
near the tables directly, but using them from a form.

So, what exactly is this database supposed to be doing why are columns being
added?

 

[Corcovadocowboy]

Hi Boblarsen,

thank you for your answer. I do digital mapping for agriculture and the
mapping system I'm using (TNTmips) is feeded by Access.

The farmer is able to modify the values in Access to see the changes in his
mapping system. My concerning is to prevent an accidental missuse of the
Access table. If the farmer inserts accidentaly a column in the first place,
the link breakes and has to be established.

You mentioned a form; is it possible to lock access to the access table and
the farmer uses a form, where it's not possible to insert a 1st column?

Thanks
gábor szakács

 

[Douglas J. Steele]

Allowing users to modify data in tables is pretty basic. Allowing users to
modify the design of the tables themselves isn't.

You still haven't answered Bob's question as to WHY your users have the
ability to add columns!

 

[Corcovadocowboy]

Hi Douglas,

as you probably have noticed, I'm not a professional access user.
You asked, why my user has the ability to add columns. I want the user not
to have this ability. How can I accomplish that in Access?

Thanks
gábor szakács

 

[Douglas J. Steele]

Simplest way (although not foolproof) would be to hide the database window
so that they don't see the tables to muck with them!

 

[Corcovadocowboy]

Ok, I will do that. Thank you.

gábor

Simplest way (although not foolproof) would be to hide the database window
so that they don't see the tables to muck with them!