 |
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
|
|
|
|

July 9th, 2004, 09:56 PM
|
|
Authorized User
|
|
Join Date: May 2004
Posts: 52
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Reference Libraries
Hello Helen.....glad to see you reviewing the forum, looks like you hit every item posted. Thanks for a great reference book.
Question: It seems like many of the problems are related to missing references. Can you point us to a master listing of all the references needed to support the book's examples? If one does not exist, could you provide one here on the forum, and perhaps add it to any errata listings that are created?
Thanks again, looking forward to your next book (don't even know the subject yet:D).
|
|

July 12th, 2004, 09:18 PM
|
|
Authorized User
|
|
Join Date: May 2004
Posts: 26
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Missing (or wrong version) references are so often a problem with Access. The databases don't all need the same references; most need a reference to the DAO object model, but only some need references to Word, Outlook or Excel. Missing references may give an error message that actually says that a library is missing (or some such), or a much less informative (not to say inaccurate) message pointing to a string manipulation function such as Chr or Left. In any case, open the References dialog from the Tools menu in the Visual Basic window, and you will see which references are missing -- they are marked "MISSING".
So far the main problem seems to be that the Replace library (which supports the Find and Replace add-in) hasn't been installed. This library is needed to support my LNC Rename add-in, and an executable compressed file, Repl9.exe, is included in the zip file for the LNC Rename add-in. Once FAR is installed, the error on its library should clear up.
Helen Feddema
Kerhonkson, NY
[email protected]
http://www.helenfeddema.com
Read Woody's Access Watch
http://www.woodyswatch.com/waw/
|
|

July 12th, 2004, 10:43 PM
|
|
Authorized User
|
|
Join Date: May 2004
Posts: 52
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Thanks for the explanation Helen. I think I can follow that OK.
|
|

September 30th, 2004, 05:33 PM
|
|
Registered User
|
|
Join Date: Sep 2004
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
I think that you had better write and erata sheet for this book. The very first install in Chapter 2 (page 44) has the following problems:
|
|

September 30th, 2004, 05:40 PM
|
|
Registered User
|
|
Join Date: Sep 2004
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Sorry for the incomplete post above.
think that you had better write and erata sheet for this book. The very first install in Chapter 2 (page 44) has the following problems:
1. It assumes that you are logged in as administror (path for installing add-ins)
2. It shows all of the addin-ins for the book installed.
3. The Design Scheme addin seems to require the same "project / reference " items listed here to for chapter 7 to be installed.
The replies here assume that you are familiar with VBA. Note the Helen's reference to tools | references menu "assumes" that you know that this is in the VBA debugger and not Access which the book is about.
I have seen several enteries about taking the book back. I too am considereing this.
--
Dave Snow
|
|

October 3rd, 2004, 06:20 AM
|
|
Registered User
|
|
Join Date: Oct 2004
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Quote:
quote:Originally posted by HelenFeddema
Missing (or wrong version) references are so often a problem with Access. The databases don't all need the same references; most need a reference to the DAO object model, but only some need references to Word, Outlook or Excel. Missing references may give an error message that actually says that a library is missing (or some such), or a much less informative (not to say inaccurate) message pointing to a string manipulation function such as Chr or Left. In any case, open the References dialog from the Tools menu in the Visual Basic window, and you will see which references are missing -- they are marked "MISSING".
So far the main problem seems to be that the Replace library (which supports the Find and Replace add-in) hasn't been installed. This library is needed to support my LNC Rename add-in, and an executable compressed file, Repl9.exe, is included in the zip file for the LNC Rename add-in. Once FAR is installed, the error on its library should clear up.
Helen Feddema
Kerhonkson, NY
[email protected]
http://www.helenfeddema.com
Read Woody's Access Watch
http://www.woodyswatch.com/waw/
|
|
|

October 3rd, 2004, 06:27 AM
|
|
Registered User
|
|
Join Date: Oct 2004
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Whoops pressed wrong button.
I too have been getting reference error messages for "Chr$" and "Left" functions.
It appears that these are referenced to "Microsoft Common Dialogs 6.0". I assume that this available in Access Developer but not in Professionakl that I am using. It was shown as "Missing" in the Object Reference. I deselected it and now everything appears to be working OK
|
|

October 5th, 2004, 03:28 PM
|
|
Registered User
|
|
Join Date: Oct 2004
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
I had the issue with the reference file being missing. It took me all of about 5 minutes to find this forum and read the posts to fix the issue. Simply running the rpl9.exe fixed the issue. I am by no means experienced with VBA and I am a beginner with Access. I felt the description was adequate and the issue was clearly addressed. As for returning the book because of this, I would have to disagree. I would like to point out that with a technical book, proof/technical readers should have picked up this issue. Thank you all for bringing it up though.
|
|
 |