Hi Paul,
The OWCRating control on the subform and the OWCRating on the main form are
not combo boxes. They are one of the data fields from the Tables.
What type of controls are you using to display the OWCRating data on the
main form and the subform? Previously, you stated "These are not "text"
boxes", and you've just told me that they are not combo boxes. So what type
of control are you using? My guess at this point is that they are indeed text
box controls.
In both cases, the data type is a "Number" but one is Integer/Auto decimal
and the other is Double with zero decimal. Do these need to be exactly the
same ?
Well, certainly you cannot stuff a double that exceeds the maximum possible
value for an integer into a field with field size integer. You most likely do
not need the one to be a Double; I would change that one to Integer.
I can usually figure out how to do everytrhing using MS Access Macros, but
this one has me stumped.
Sorry, but I try to stay as far away from macros as I can. In Access 2003
and all prior versions, one cannot trap for errors and handle them gracefully
when using macros. Any errors that occur will cause a really ugly macro error
dialog to be presented to your users. The newest version of Access, Access
2007 allows for error trapping, so macros are more appropriate to consider
using for Access applications created with Access 2007. Consider the
following quote:
From: "Inside Relational Databases, 2nd Edition, by Mark Whitehorn and Bill
Marklyn, published by Springer, p 151
"Macros offer the next level down, extending the functionality of the GUI.
Macros are still limited, however, and do not provide anything like the
enormous flexibility of a programming language. Both the macro and the
programming languages take some effort to learn and, surprisingly, often
require relatively different skills; in other words, a good working knowledge
of macros may not make it much easier to convert to using the programming
language. Perhaps even more surprisingly, I do not believe that programming
is fundamentally more difficult to learn. Macros are easier to use but not by
orders of magnitude."
"If you are new to RDBMSs, I suggest (with as much deference as possible)
that you may well not be in a position to judge whether you need macros or
programming. In that case, my advice is clear. Unless you are sure that your
needs really are simple, don't bother learning to use macros. Once you find
that you need more than the GUI offers, go straight to the programming
language. In this way you avoid the pain of climbing one learning curve only
to discover that the view from the top is unsatisfactory and another climb
awaits you."
I'm not a Visual Basic programmer and just don't understand the code you
provided.
Try Access Basics, written by Access MVP Crystal:
http://www.accessmvp.com/Strive4Peace/Index.htm
MS access Help seems to imply that I can do this via SetValue.
Don't know on that one.
Does it matter that my Form names are EDIT IMCOMPLETE ENTRIES and
FIND PHRF (separated words and in caps)? Should I change the Form
names to EditIncompleteEntries and FindPhrf ? Does it really matter?
This should not matter. However, I encourage you to avoid using special
characters, including spaces, in anything that you assign a name to in
Access. You will be doing yourself a favor in the long run to adopt more
standard naming conventions.
Special characters that you must avoid when you work with Access databases
http://support.microsoft.com/?id=826763
Did you try the code I suggested, even if you may not understand it?
Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________