I'm having trouble setting up this one project because I thought table relationships were one thing, but apparently they're not.
I get a bunch of errors in my forms.
I had though cascade update would update the rest of the fields in the table on the "many" side. There is other terminology that I may be misinterpreting.
Please point me to simple, small examples of Access databases featuring relationships so I can see how they work.
Please do not attempt to explain relationshipos here. It's something that I've read over and over, and over. Also, do not refer me to that Northwind database. It's far too complex, compared to my little project at hand.
Thanks,
Jim
Do you have any software (you can use ctrl+print screen in a pinch) that will let you create a snapshot of the relationship window? Attach a shot of the actual relationship window so that I can see what other table fields you are trying to control.
Autoeng
Perhaps you could post your table relationships so that we could have a look. Then we might be able to help you.
Autoeng
:D
"Why, yes! My husband and I...."
Point me to your post on Access World.
Autoeng
Sorry I wasn't able to get to the root of your problem. I hope Dreamboat doesn't mind but I'm going to point you to another Access forum (Dreamboat shouldn't mind as she is a mod in the Office forums there). Try posting you question in the General forum at Access World http://www.access-programmers.co.uk/forums/ The people there are the most knowledgeable that I have found.
Autoeng
I really like this site.
OK, here's a zip file of a bmp
I read the page you indicated and it really did not teach
me anything new. Regarding the file names, I've used
underscored file names in previous Access 97 databases,
(but not in ones where I needed to make multiple references).
I think my table design is good. I have uploaded a graphic in a previous post, indicating my relationships, and I ask you to look at it too.
The one change I had to make is I removed the relationship between Customer_Data and Service, thanks to the kind suggestion from your fellow staff.
Anyway, I posted something last night, and hope Lightning will get back to me.
Thanks,
Jim
I don't know whether this will help. The bookAccess inside out is well written when it comes to the essential stuff of ACCESS though it doesn't deal so much with programming. It has an accompanying CD which contains sample databases among other things. I have actually not opened it but I know that other books have simple examples. It might be worth getting this book or something similar.
Best Wishes.
Graham
p.s. I have found that the extra constraints added to ,linkages cause all sorts of problems. Thus if I open a form and then try to close it without entering data, or if I miss data then the form will not close if the linkage demands data in the many side of the table. It then becomes a big coding problem on the close form button to check that each of the controls that should have data is properly completed. I am therefore leaving this extra capability out with the ida that I can re-edit specific control and add the necessary code when I have the DB running. I guess I am just lazy. The other problem is that 20 forms later when something crashes you forget where the problem lies and it takes an effort discover that the requirements on a relationship are at the root of the problem rather than coding errors etc.
Thanks for your response.
Here are the 3 tables and their relationships:
| (Customer_Num) | (Customer_Car) | (Service) |
| Customer # is (PK) | Customer # (many) | Customer # (many) |
| Unidque_ID is (PK) | Unique_ID is (many) | |
I know there's nothing complicated about the set up and it should work, but I keep getting the 3021 errors "you can't update . . . related record required . . ", and I'm not violating any fundamental rules.
Another pop-up error I get is
438 "Object doesnt support this property or method", when I'm in my database view, and I manually click on the main form and the Customer_Equipment subform. That's when I get the pop up error. When I click on the Service subform to open it, it does NOT happen.
Does that provide any more insight into my situation?
Thanks for taking a look,
Jim
Thanks for the tips earlier today. I modified the tables as you suggested, but there are still the same problems. But I'm sure I was causing unecessary indexing work the way I had it.
Jim
By the way, Jim, I'm willing to look at your DB too. You've got my addy.
Thank You for the help in this post.
I went to the site that Autoeng stated, and actually got my problem solved. It wasn't a matter of code, at all.
Instead of having one main form and 2 separate subforms, I could have dropped one of the subforms on top of the other one, and that would have provided another set of master/child links to apply. I had no idea I could do that.
I'm going to back to consult my BIG FAT GRSSK ACCESS book to see if I missed that feature
while searching it previously.
Thanks again,
Jim
Autoeng
Like Autoeng says, spaces in your field names will just cause your expressions to be more difficult to write, and you can get in big trouble by having symbols in your field names. It's best if you can write them something like this:
FieldName
That makes them easy to read, but keeps them to one word.
You'll be able to make them easier/faster to use later if you change "Customer" to "Cust". Your CAPTIONS should read exactly what you want the user to read--not the field names.
Yes, I know about the snapshot, but where to send it ?
I prefer not to use my web space. Is it possible to email it directly to you, to look at ?
Jim
I don't think that you need to create a relationship between tables Customer_Data and Service nor do you need Customer Number in Service. Try that or convince my why you do.
A tip for the future. Don't put spaces in field names.
Autoeng
I DID go back and change all the names to all my table names, etc. to make them without spaces, like I believe Dreamboat suggested. I still have the same problems regarding the "438" message, but I'm sure there's a solution somewhere.
I will check out the site that Autoeng suggested. But will definitely post more questions for this group.
Thanks,
Jim
#If you have any other info about this subject , Please add it free.# |
