Chris,

>This is what I hear you saying:
>
>1. "Experts" have advised not to use native keys
>2. You, or someone on the project before you, used native keys
>3. Now native keys are causing a problem
>4. The "experts" tell you you should not have used native keys.

Eh? You hear me saying that? I wasn't even talking about the native key discussion...I was talking in general about how some questions get answered with responses about design and methodology more than just answering the question directly. My example would be scrollable forms. The first post answering any questions about scrollable forms invariably states: "scrollable forms are BAD". Poppycock. Someone may have a very good reason to use scrollable forms (and they shouldn't have to explain themselves), and may be on the verge of a revolutionary new interface that will bring Bill Gates to his knees. OK, maybe not...but do you see my point? A question should be answered. If the person who asked then needs more help, then help them. Yes, there are obvious ones like: "I have never used Fox before...help me with the SAY and GET syntax" Yes, in that case I would say it is better to tell the poor soul that we don't really use SAYs and GETs anymore.

But when the questions deal with database normalization, or key generation, or remote views vs. SQL passthrough...these questions should just be answered straight-up and not laden with personal diatribes on how some processes are "lousy" while others are manna from heaven. Examples of good answers include example code and URLs to web sites or names of books for further study. Examples of a bad answer are things like "well, we tried that and it sucked", or "you are better off just avoiding that whole area because it is non-standard". Thoses kinds of answers are non-helpful at the best, and grating at the worst.

>Sorry, I just don't see how you can get ticked off at the experts. There are a number of people on here who's advice is almost as good as gold. Anything Ed Rauh writes is my religion. < g >

And if Ed Rauh answers my question straight up, I will appreciate it. If I say "I am stuck with this indexing scheme...can you help", and his only answer is "start from scratch", then that's great, but I doubt that would be the only answer Ed would have.

BTW, I don't get ticked off at the experts, and I have never berated anyone who answered my questions, privately or publicly. I generally just do what we all do...grumble to myself, forget about it, and once in a while post a small rant, as I just did.

>If they tell me it's bad design, I don't take it as gospell, but pretty darn close. And I don't take it personally.

Nor do I. But if the bad design is there and cannot be changed, then give me something I can use...don't just tell me I am screwed -- I probably know that already. *grin*

>But if I don't take their advice, I don't ask them to fix it when I run into trouble.

Nope, nor would I. If I ask how to use SAYs and GETs and then later realize I should be using forms and textboxes, I am not going to yell at someone for not telling me there was a better solution out there. There is _always_ going to be a better solution out there -- a programmer needs to find some of those for him/her self.

JoeK