Avoidinhg changes of ACCESS tables repectively query properties for end users

[Winfried Kastner]

Hi,

I have one question. I have to write a big ACCES 2003 (with Windows XP)
application with many (big sized) tables and queries. It is desired that
these tables and queries should not be hided for the end users but viewable
for them. (By the way I also want to avoid any user adminstration inside
ACCESS.)

Thus the end users could change layout features e.g. the width of colums or
can move them to another place or they can they click on the sort icon to
sort the table or query in another way. To do such sorts by the end users is
ok but I want to avoid that this new sort property will be the new "default"
for the next request. I possible I also want to "redo" my format definitions
when the tabel or query will be closed. Ok, when you leave the table or
query after you did a change you will be asked "There was a change in the
table/query. Do you want to save these?". But often it happes that you press
of "Yes". If possible I want to have a kind of suppressing the "Yes" button.
That would be perfect but I don't now how t achieve this.

If possible I want to avoid such things in order to display the tables and
querys always in the same layouts I (!) defined!! For tables and queries I
want to have a kind of lock for the "Filter", "Order By" (in table
properties) and as well the format changes.

I searched in many books and in the internet (web, groups) how to program
this but unfortunately I found n solution.

For e.g. when my ACCESS application will be started it would help to "go"
with ADOX through all tables and querys and to "blank" possible texts that
exits in the prperties "Filter" or "Order by". This means I want to do this
kind of reset during runtime. Unfortunately I fund no way how this can be
programmed with ADOX if it's actually possible with ADOX. Or does there
exists another solution?

I really would appreciate any hint how to solve my problems.

TIA
Winfried

 

[Winfried Kastner]

Hi Joseph,

I have all the mentioned tables defined in several ACCESS tables (as
back-end). All ACCESS mdb-files are available and stored on a network drive.
In my application I have links to these tables. But I want to avoid to
rename them starting this prefix "sys" as system defined tables that are
normally hided.

The application I write will only be used by one or two colleagues and I
think they will "carefully" use it. And it will make sense that my
colleagues will have a look into the original ACCESS tables and four other
linked SYBASE available as data base views.

The applicaton will surely be one of those with many changed through its
life-time cycle. Ok, if all will run well, I can hide the whole database
window because the application is already driven only with the usage of
forms that do all the queries etc with click on buttons.

Regards,
Winfried

 

[Albert D.Kallal]

I think, in the long run it is best to build, and layout the application.

That way, users don't need to "learn" how to lay things out.

Do all of the hard thinking for them!!

here is some screen shots of tables of data, but forms were used, and thus
uses never actually see the underlying application.

http://www.members.shaw.ca/AlbertKallal/Articles/Grid.htm

in fact, many users don't even know it is ms-access....

If you spend a bit of effort and time, you should be able to design a UI
that meets the needs of the users, but they can't change it...