A
aehchua
Hi all,
I was wondering if someone can help me. I teach a database class at
Nanyang Technological University, Singapore and am looking for a VBA
(Access) textbook to complement the database material I teach. This
book should have the following characteristics:
(1) Preferred: NOT be an introductory programming textbook. All of the
books I've reviewed teach things like variable declaration, arrays,
etc. That's all fine, but my focus isn't there. Too often, authors of
these books are exhausted by the time they finish arrays.
(2) Preferred: By McGraw-Hill. I use a McGraw-Hill database textbook,
and a McGraw-Hill systems analysis and design textbook. If the book is
by McGraw-Hill, the students get a discount on the bundle.
(3) Required: Teach advanced relationships between forms and databases.
Some of the ideas I want include:
(a) The concept of unbound forms. This is a database class. They're
supposed to do SQL things like insert and update. I want a book that
teaches them Select... if rs.eof then insert else update.
(b) time-motion effects. So these would be things like- try not to
force the user to use the mouse because for massive data entry, pure
keyboard is faster. The system should automatically go to where the
user is going to go next. For example, if one is marking examination
scripts, a save should automatically move to the next student.
(c) accomodating reality. Managing level of validity controls,
allowing the user to save temporary data (e.g., on a long form where
the data entry person spots an error. The form should allow the data
entry person to exit gracefully, correct the error and come back to the
form without having to retype everything all over again).
(d) mapping several records to a single form (e.g., like in an invoice
which will have many items). Subforms should be described as ONE
solution and subform solutions should not write directly to the
production database (to maintain the idea of unbound forms). Simulated
arrays (e.g., where form controls are called things like item1 item2
etc.) should be offered as another. Paging algorithms (e.g., the
simulated array has 10 lines. You click on a button to go to page 2
where items 11-20 are displayed) should be described. The idea that a
combination insert and delete is equivalent to an update (makes these
kinds of forms possible to manage).
(e) strategies for handling multiple open windows (e.g., forcing
windows to be modal). I'm not looking at writing complex code as much
as I am looking for strategies by which a programmer can make his or
her life easier when he or she must use multiple windows.
(f) proper screen layout- English speaking people read from left to
right, top-down, so the screen should be like that. Search options
should appear here, data entry should appear here, one should be
disabled if the other is active, etc.
(g) managing the search of composite attributes.
(i) designing screens to both search by and update primary/candidate
keys.
(j) handling multiple users on a single application. This is not
just table and record locking, but also the idea that two people can be
editing the same entries on two different forms. The forms should
alert users to these issues.
In other words, I want a book that gives students a good idea that the
user interface and database often do NOT correspond. I also want a
book that introduces students to the difference between user
requirements, design, and implementation where design/implementation
includes things to make the programmer's life easier.
Cecil Chua
I was wondering if someone can help me. I teach a database class at
Nanyang Technological University, Singapore and am looking for a VBA
(Access) textbook to complement the database material I teach. This
book should have the following characteristics:
(1) Preferred: NOT be an introductory programming textbook. All of the
books I've reviewed teach things like variable declaration, arrays,
etc. That's all fine, but my focus isn't there. Too often, authors of
these books are exhausted by the time they finish arrays.
(2) Preferred: By McGraw-Hill. I use a McGraw-Hill database textbook,
and a McGraw-Hill systems analysis and design textbook. If the book is
by McGraw-Hill, the students get a discount on the bundle.
(3) Required: Teach advanced relationships between forms and databases.
Some of the ideas I want include:
(a) The concept of unbound forms. This is a database class. They're
supposed to do SQL things like insert and update. I want a book that
teaches them Select... if rs.eof then insert else update.
(b) time-motion effects. So these would be things like- try not to
force the user to use the mouse because for massive data entry, pure
keyboard is faster. The system should automatically go to where the
user is going to go next. For example, if one is marking examination
scripts, a save should automatically move to the next student.
(c) accomodating reality. Managing level of validity controls,
allowing the user to save temporary data (e.g., on a long form where
the data entry person spots an error. The form should allow the data
entry person to exit gracefully, correct the error and come back to the
form without having to retype everything all over again).
(d) mapping several records to a single form (e.g., like in an invoice
which will have many items). Subforms should be described as ONE
solution and subform solutions should not write directly to the
production database (to maintain the idea of unbound forms). Simulated
arrays (e.g., where form controls are called things like item1 item2
etc.) should be offered as another. Paging algorithms (e.g., the
simulated array has 10 lines. You click on a button to go to page 2
where items 11-20 are displayed) should be described. The idea that a
combination insert and delete is equivalent to an update (makes these
kinds of forms possible to manage).
(e) strategies for handling multiple open windows (e.g., forcing
windows to be modal). I'm not looking at writing complex code as much
as I am looking for strategies by which a programmer can make his or
her life easier when he or she must use multiple windows.
(f) proper screen layout- English speaking people read from left to
right, top-down, so the screen should be like that. Search options
should appear here, data entry should appear here, one should be
disabled if the other is active, etc.
(g) managing the search of composite attributes.
(i) designing screens to both search by and update primary/candidate
keys.
(j) handling multiple users on a single application. This is not
just table and record locking, but also the idea that two people can be
editing the same entries on two different forms. The forms should
alert users to these issues.
In other words, I want a book that gives students a good idea that the
user interface and database often do NOT correspond. I also want a
book that introduces students to the difference between user
requirements, design, and implementation where design/implementation
includes things to make the programmer's life easier.
Cecil Chua