Recent content by golfortennis1

Ok, I think I see it now. I was getting stuck on the same number appearing multiple times without a differing characteristic in the same field. Trying this out now.

So the fact the same number would show up multiple times in the distancetopin column wouldn't be an issue?

On the shot values discussion, the problem would be that you have F10, for example, but then there is G10, R10. So if the distance is a field on its own, 10 would show up multiple times. And you need the different values, because 10 yards from the fairway you would be expected to get down in...

Made a few adjustments.

Thank you. I actually have gone back and updated the other tables to relate the autonumber primary key. Now that I have the shot data form as the primary input, and I can make the club/lie/ etc., visible for the choice, but feeding the primary key to the tblshotdata, I should have not only...

I thought I had moved ahead but then the referential integrity item was brought up. I'm assuming those who have posted read the thread from the beginning. The referential integrity for the shotdata table will be fine, I can easily change the data to the autonumber, and then make the form do...

If I understand you correctly, the problem there is there is no guarantee as to what club you are using for a given shot. F150 may be an 8 iron one day, and a 6 iron the next. The wind, elevation, where you want to leave your shot all play into what club you hit. On the input form you input...

So the Club in question is the item used(Driver, 3wood, pitching wedge, etc.) Other than adding a different club to the list(put in a 5 wood for one round), I can't see that list ever getting larger than about 20 or so. By rule you can't change clubs within a round, a person can't make a...

The only string join I can see happening is the one discussed earlier. The rest are for classifications that won't combine. So, trying to think this through, would you say I should, similar to what I have with course name on my frmShotData, I should do the same with some of the others(ie...

So I have to admit that question went through my mind. Why have the unique ID? The advice given earlier in the thread was to have the ID, but if referential integrity is important(which in some cases, for this particular project I'm not so certain it is), this would need to be the solution...

Update: I have brought in referential integrity to every one of them. Changed the autonumbers into long integer number and it seems to have handled it.

Ok, I thank you for taking this time. I can put my primary keys on Club, Lie and Type in their respective tables rather than the ID. BUt my IDs in some of the others are autonumbers, so I'm not sure where how to fix the errors. I've looked up referential integrity to see what is needed, but...

Nice...lol. Never heard that one.... historical roots Sheep Pasture would fit real nice!!

I will assume you are referring to me and not Cowpaturepool.... I thank you for the kind words. It would seem like it should be obvious, but these folks don't *need* to help, they are choosing to. Attitude would be showing disrespect to that fact. I can't say I have been such a positive away...

Thank you. Now, please, really don't tell my wife!! :)