Replies

Boy, what an adventure! It’s difficult enough stumbling around in the jungle watching for snakes, but doing it without a compass is nearly impossible!

I went back and looked at the tblMaster where the forms get their data and discovered (as you have pointed out) that the Release1No is, indeed, a text field. I also discovered, as I was about to change it to a numeric field, that this number is given to us by the shipper and “may” contain text as well; whereas the ProNo is an in-house number (auto). The field “name” is misleading (as you also pointed out) and I am considering changing it, but it is used in so many different references that it may not be worth the effort.

I have learned a few valuable lessons here. Naming conventions can be (are) critical to the reading of code, both for the user and the creator. I have purchased several books on Access and, recently, VBA; but having the text doesn’t necessarily mean that you will even be able to locate the answers (it’s a big jungle). I am discovering the value of being able to write code, and obviously the dismay associated with what only appear as “minor” errors. I am most grateful for resolving the problem, but even more so for having learned something new that I can take with me into the jungle.

I don’t want to get all emotional here, but this is one VERY grateful newbie. Not only were you willing to address the immediate problem, but were willing to go the extra mile in explaining the code. Thanks for providing a compass!

I FIXED IT
Thanks for your input! (please see thread)

I FIXED IT!

Original code:
stLinkCriteria = ” [Release1No] = ” & Me ! [Release1No]

Modified:
stLinkCriteria = ” [Release1No] = ” & ” ‘ ” & Me ! [Release1No] & ” ‘ ”

Before anyone thinks I’m a 52 year-old “boy” genious, I stole the code from the cmdButton. The only problem I have now is that I don’t know why the modified code works. I have corrected the problem, but I haven’t learned anything (other than how to “steal” code). I very much appreciate your input (especially concerning “Dirty”), would you mind explaining why the modified code works? Also, if you would be so kind, why the original code works just fine for ProNo_DblClick, but not for Release1No_DblClick? Should I also change the code for ProNo_DblClick (even though it IS working just fine)?

Thanks again for your generousity!

The “ProNo” and “Release1No” are assigned at the time of order entry and should never be editied by the operator (if that makes any difference). The ProNo is an autonumber field and the Release1No never changes after the original entry. Not being real certain of what I’m doing here, I tried a little experiment:

I kept the code for “Release1No_DblClick” the same except I changed the stDocName to “frmBillOut” (seeing as that form opens without any problem from “ProNo_DblClick”). I get the same error message as before.

I changed the code back to what it originally was, added a cmdButton for frmOrderDetail, and it works just fine.

I suppose I can live with the cmdButton, but it’s inconsistant with the way operators attain information with other forms. The DblClick function is the way things are normally done. Also, and seeing as I AM a newbie, I want to understand what’s going wrong so I can gain some knowledge here. I just don’t get why a cmdButton (applied using a wizard) would work just fine, but the DblClick would fail; and especially in light of the fact that the dblClick from “ProNo” also works just fine when opening frmBillOut. I actually thought that David was on to something when he asked about the properties for frmOrderDetail, but seeing as it works just fine from the cmdButton, I’m not so sure that’s the issue either.

Thanks Hans, it didn’t fix the current problem but I now understand how important that “Dirty” issue could be. As a newbie to VBA, I appreciate every bit of guidance.

There are no event properties for frmOrderDetail

Thanks Drew! I finally got around to reviewing it. Very helpful for a newbie!

…and still maintaining a good sense of humor. Gotta love that!

Sorry, I didn’t mean to offend any of my peers!
Thanks for the forum tip; I will do so in the future.

I really didn’t “inherit” it so much as it inherited me, I guess. The company I was working for went out of business, and I was offered some of the old equipment at “bargain” prices a few weeks later. Everything had kind of been piled up in one room with boxes of towers, keyboards, monitors, printers, etc. I really was looking to see if the old server was still around or maybe some of the later model PC’s, but most of the “good” stuff had been liquidated. I ended up taking a box that had two towers (one with a tape drive), a bunch of cable, and at the bottom a bunch of loose floppies, manuals, and CD’s. I was going to pull everything out and just dump it into another box, but the cables were all tangled up with everything and there were no empty boxes anyway – so I took the whole thing home to clean out there. It sat in the corner of my home office for 2 weeks before I started going through it all.

At the very bottom of the box, under all the manuals and scattered floppies was this UN-OPENED box labled “XP Developer”. I didn’t even know what it was. I opened it up and find 7 CD’s inside with things like Media Content, SQL Server, Exchange 2000, Visual SouceSafe, Developer, and Office XP w/FrontPage. I didn’t know what the other stuff was, but I knew what Office XP was and I got, well, a bit giddy. Really, I was like a kid on Christmas morning. Why? Because when I got there I found out that they weren’t taking any checks and I only had $47.00 in cash on me. I knew the tape drive was well worth the money (even though its rather dated) so they took what I had on me just to get rid of the “garbage”.

Sorry I rambled on so long, but it’s rare that I encounter such good fortune, and felt a need to share with someone who could appreciate the story (my daughters just looked at me blankly and said: “That’s nice”). Anyway, now I feel somehow obligated to learn VBA so as not to jinx the genie in the bottle so to speak.

Thanks again Hans! (Please see previous)

Thanks! I suppose if I’m going to get anywhere with this VBA lesson, I’m going to have to get away from the “point and click” mentality. At 52 it’s even difficult getting past the “…old dog, new tricks.” syndrome. I managed to inherit XP Developer, which got me interested in this whole VBA thing to begin with. Having Developer, with my level of expertise, is a little like giving a Ferrari to a 13 year-old, but, what the hell; I’m willing to give it a shot!

Option Explicit was not checked, and even when I changed it in Options it did not appear in that module. I opened a new module and it DID appear. I went back and re-created the subs from the lesson and everything is working fine now. I suppose you can’t change the options in an active module once the routine has been entered? Anyway, thanks for getting me back on course. BTW, I went back to the original module and just deleated the text “Option Compare Database” and entered the text from the lesson, and the routine worked there as well (although it isn’t Option Explicit). Thanks again for your help.

Sorry I missed your last post, but I was on my way out the door.
I’m in California and noticed that you were “down under”. As a fan of Fosters, I made the offer if you ever were out this way.
I’m a “newbie” to Access as far as doing any developement, but managed to “inherit” the Office XP Developers Version. Of course I don’t even know what I’ve got yet, but I did manage to get up the gumption to buy a copy of Beginning VBA. I can’t even remember how I found this site but I sure have enjoyed the exchanges and generous helps. There are some very compationate and helpful people here that put aside ego to assist those who are just trying to get started. That’s pretty rare in any forum. You’re a prime example of what I mean. What was probably a very simple matter to you had become a great source of frustration to me. It seems that MS sells their products with vague or limited documentation and just says “good luck”. People are left staring at the screen with their finger poised over the mouse not wondering where they “want to go today”, but rather how to get there. If not for friendly users, I’d never get to the first “click”. When I say “thank you” for your help, it’s really much bigger than the words can say.

You did it John! It works great!
Thanks again for all your help!
If you ever make it to the colonies, I owe you a Fosters or two, or three, or…