Wrox Programmer Forums
| Search | Today's Posts | Mark Forums Read
BOOK: Expert One-on-One Access Application Development
This is the forum to discuss the Wrox book Expert One-on-One Microsoft Access Application Development by Helen Feddema; ISBN: 9780764559044
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Expert One-on-One Access Application Development section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
  #1 (permalink)  
Old July 3rd, 2004, 07:48 AM
Authorized User
 
Join Date: Jun 2004
Location: Cumberland, MD, USA.
Posts: 43
Thanks: 0
Thanked 0 Times in 0 Posts
Default UnCalled CheckData

The last paragraph on p.265 states "This is done by calling a procedure called CheckData from various control AfterUpdate procedures." The entire Code Behind Forms module for fpriOrders is presented on pp.266-273, but I can't find a single time that the Sub procedure CheckData is called. Am I missing something here?

Terry Waltz
__________________
Terry Waltz
  #2 (permalink)  
Old July 3rd, 2004, 05:26 PM
Authorized User
 
Join Date: May 2004
Location: , NH, USA.
Posts: 52
Thanks: 0
Thanked 0 Times in 0 Posts
Default

See page 271, 4 lines from bottom for Sub CheckData(). The routine continues through all of page 272.

I believe that you must have CheckData() triggered in the After Update Events for cboToyID, cboCustomerID, cboEmployeeID, txtOrderDate, txtRequiredByDate, txtPromisedByDate, and txtToyQuantity fields.

It could have been explained more explicitly, but she does explain that she needs the Customer, Employee, and three dates filled in, and those are the fields noted in the routine.
  #3 (permalink)  
Old July 3rd, 2004, 07:31 PM
Authorized User
 
Join Date: Jun 2004
Location: Cumberland, MD, USA.
Posts: 43
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I realize that the Sub procedure CheckData (and its VBA code) exists (pp.271-273). But just the existence of a CheckData procedure is not enough. The CheckData procedure must be called from some where in order for the code to be executed. Take a look at code for the AfterUpdate events that you mentioned. Except for txtToyQuantity, all of the After_Update events for these controls call EnableQuantity. B U T EnableQuantity does NOT call CheckData. So how does CheckData get run if it is never called?

If you search all of the code listed on pp 266-273 you will not find a single place where CheckData is called. Going one step further, if you do a search for the text "checkdata" in the "downloaded" database files you can't find any place where CheckData is called. So how does CheckData get run if it is never called?

Terry Waltz
  #4 (permalink)  
Old July 3rd, 2004, 11:07 PM
Authorized User
 
Join Date: May 2004
Location: , NH, USA.
Posts: 52
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I will repeat a portion of my earliet posting that I guess you may have overlooked:
=================================================

I believe that you must have CheckData() triggered in the After Update Events for cboToyID, cboCustomerID, cboEmployeeID, txtOrderDate, txtRequiredByDate, txtPromisedByDate, and txtToyQuantity fields.

It could have been explained more explicitly, but she does explain that she needs the Customer, Employee, and three dates filled in, and those are the fields noted in the routine.
===============================================
  #5 (permalink)  
Old July 4th, 2004, 01:53 AM
Authorized User
 
Join Date: Jun 2004
Location: Cumberland, MD, USA.
Posts: 43
Thanks: 0
Thanked 0 Times in 0 Posts
Default

You are correct when you say that "you must have CheckData() triggered in the After Update Events for cboToyID, cboCustomerID, cboEmployeeID, txtOrderDate, txtRequiredByDate, txtPromisedByDate, and txtToyQuantity fields".

B U T the author fails to to do that, even though she said she DID in the last paragraph on p.265

Terry Waltz
  #6 (permalink)  
Old July 4th, 2004, 11:36 AM
Authorized User
 
Join Date: May 2004
Location: , NH, USA.
Posts: 52
Thanks: 0
Thanked 0 Times in 0 Posts
Default

You said: "B U T the author fails to to do that," Curious to know how you determined that. In the downloaded code? I have not personally gotten that far in the book yet.

I can't speak for the author, or provide any explanations re the final book content. I am just trying to help you get your application working.
Good luck....
  #7 (permalink)  
Old July 4th, 2004, 02:00 PM
Authorized User
 
Join Date: Jun 2004
Location: Cumberland, MD, USA.
Posts: 43
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Curious to know how I determined that? I explained that in a previous post, but here goes again ...

On p. 265 (last paragraph) the author states "I could modify the txtToyQuantity BeforeUpdate event procedure, but it's less cumbersome to just make txtToyQuantity disabled initially, and enable it only after all of the relevant fields have been filled in. This is done by calling a procedure called CheckData from various AfterUpdate procedures. ... The entire Code Behind Forms module for fpriOrders follows."

Note that the code on pp 271-273 includes the Sub procedure named CheckData. I think that it is pretty obvious from that text that the author intended to impliment CheckData to ensure that "all of the relevant fields have been filled in". Wouldn't you agree?

B U T no where in the code shown on pp 266-273 is CheckData called.

If you go one step further and check any of the downloaded databases (i.e., Toy Workshop (Life Cycle Finish).mdb) you will find that the Sub procedure exists, B U T again no where in the code shown on pp 266-273 is CheckData called.

I can't speak for the author either. I just wish the author would speak for herself on this matter.

I would submit this as an errata, but based on my recent past history submitting errata they (Wrox/Wiley) have the procedure for submitting an errata really messed up right now. It's no wonder that there are no errata list for this book.



Terry Waltz
  #8 (permalink)  
Old July 8th, 2004, 07:18 PM
Authorized User
 
Join Date: May 2004
Location: Kerhonkson, NY, USA.
Posts: 26
Thanks: 0
Thanked 0 Times in 0 Posts
Default

The CheckData sub is in the CBF module for fpriOrders, but it isn't called -- looks like I replaced it with the calls to the EnableQuantity and EnableShippingAddress procedures, but forgot to change the text.

Helen Feddema
Kerhonkson, NY
hfeddema@hvc.rr.com
http://www.helenfeddema.com
Read Woody's Access Watch
http://www.woodyswatch.com/waw/
  #9 (permalink)  
Old July 27th, 2004, 10:30 AM
Authorized User
 
Join Date: Jun 2004
Location: Cumberland, MD, USA.
Posts: 43
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks for your confirmation.

Should I post this as an Errata? (I haven't had any confidence in the Errata procedure since I get no feedback and no Errata have been posted on the website) Or will you take it from here?

Terry Waltz






Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.