Datasheet Properties

  • Thread starter Thread starter Chris
  • Start date Start date
C

Chris

Hi,

I'm exploring the use of the datasheet layout in some subforms. Using this
layout is a nice way to maximize on field real estate and providing sorting,
in-field filtering, column re-ordering/hiding etc. However, I find that
some aspects of these options too powerful, in that one user's change
affects everyone. E.g., if a user re-orders or hides a column, this setting
remains with the datasheet.

Minimally, I'd like to discard any changes the user made to the datasheet
settings. Ideally, I'd love a way to save their choices and apply them back
each time they access a certain set of records, but first things first. How
can I enforce my minimal requirement of preventing a single user's change
from being permanent?

Chris
 
That is the reason many developers go away from datasheet view to continuous
forms view. But I still like the column width and ordering capability of
datasheet view too. Best seems to be to set or clear the filters etc during
form open event. I think you can also set the column widths there too. You
can lock and unlock columns, although whenever I tried this I always ended
up locking columns the users wanted to change. You can also prevent users
saving the form by catching the event in code, which avoids most of the
problems.

When you say 'one users change affects everyone' does that mean you have
several users on different computers using the one copy of the form over a
network ? If so, that can be a disaster. Split your database, and give
each user a copy of the front end on each machine, linked to a back end just
containing the tables.

--
Regards,

Adrian Jansen
J & K MicroSystems
Microcomputer solutions for industrial control
 
Silly me. I am splitting my database and distributing my front end. I
forgot about this when I was working on the development copy on two
different computers.

I will still investigate the options you gave, since I don't want the users
to unintentionally hide columns that should, for the sake of application
design, be shown. If I have any questions, I hope you'll help me out?
E.g., I'm not sure yet how to address the column widths of the fields in
their datasheet presentation (since the underlying form's properties are
just that of text boxes) but I will research.

Thanks,

Chris
 
Back
Top