Field Population (1 Viewer)

supercharge said:
Lucky you for having those kinds of customers or bosses.

I'm feeling sorry for you, Sarah, for having to deal with an existing database that is a mess. If you want to normalize it, I hate to say but, you may have to start over which I don't think you'll do anyway because you have forms, reports, queries and .... depend on the tables and it'll be a pain in the butt (see my signature?).

Very lucky in deed, I know the kind you are talking about and that is mostly the way mine is! Yeah I dont really want to start over, and I though that I was normalized farley good.
 
oh Okay so can we get back to the problem that I was having supercharge! all these posting is getting a bit confusing. Anyone who would like to help me that is great, but you have to take it down a notch and start at the beginning. seems like this form is getting a bit high stressed maintenance :)
 
reclusivemonkey said:
I think you are totally wrong here.....

I totally agree, sometimes what we need are people managment skills as much as db management skills. If your boss, client, user is making your life difficult finding a way of managing them is just as important as delivering what they want.
 
reclusivemonkey said:
...If you were a builder, and saw an apprentice building a wall on unsuitable foundations, would you help them build the wall up regardless?..

If I were responsible for "the wall" then no, I wouldn't. But if not, I would talk to the apprentice about all the rights and wrongs but again, it would be up to the apprentice whether he wants to listen to you or not, right? And if you knew that he wouldn't listen to you then why bother, right?

Wow! I'm enjoying this thread, wish it could go on and on!
 
supercharge said:
If I were responsible for "the wall" then no, I wouldn't. But if not, I would talk to the apprentice about all the rights and wrongs but again, it would be up to the apprentice whether he wants to listen to you or not, right? And if you knew that he wouldn't listen to you then why bother, right?

Wow! I'm enjoying this thread, wish it could go on and on!

Ok but what if you had to put a roof that you are responsible for on the wall that you are not?
 
supercharge said:
but again, it would be up to the apprentice whether he wants to listen to you or not, right? And if you knew that he wouldn't listen to you then why bother, right?

Hmm, well I didn't quite create an exact metaphor... This is a forum. EVERYONE posting for help IS asking; anyone who asks for help and doesn't listen is foolish in the extreme...
 
That would be a different story, Stoat.

Anyway, why did I just help, but not correct? Because I knew that Sarah wouldn't start over her databases, after working with her for quite some times thru PMs and emails. That's it, simple.
 
reclusivemonkey said:
Hmm, well I didn't quite create an exact metaphor... This is a forum. EVERYONE posting for help IS asking; anyone who asks for help and doesn't listen is foolish in the extreme...


Were you around for Mike375? :eek: :D
 
When I joined this forum I knew nothing about Access, but I had a lot of Paradox development under my belt, but zero formal training. When I started asking questions, I started being pointed at normalisation. It took a few times for me to take notice, but since then Ihave realised that normalisation is not a problem solving approach, but a problem avoidance approach.

When I give adivce in here, I will help people that have un-normalised structures, but I will point out there mistake.

The difference in Sarah's original question, is that adpting a normailsed structure would be easy and the problem would then dissapear. Supercharge seems to be determined to chip code out of granite when a simple one-to-many relationship would be so much easier.

Still, it's a free forum and if folks seem determined to stick to the stony track, that's their choice.
 
Last edited:
If the posts are still here, the sort of. If you fancy reading the thoughts of a no-brain Access user with racist proclivities.
 

Users who are viewing this thread

Back
Top Bottom