Copying a button and precedure in Access 97

N

NES

I have inserted a button in a form that calls in another form to show details
on a selected record. It works great. Now I have to impliment this on about
20 other forms. I know I can copy the button, tinker with the property sheet
on each, then copy the code, but is there an easier way to copy this whole
group into each form? Thanks in advance for any help.
 
N

NES

Rick, I appreciate the unwarranted criticizm. I didn't say they were similar
forms, and they are not. This reply was not helpful. Please refrain from
helping me further.
--
Norm Shimmel
Butler, PA


Rick B said:
Why do you have 20 similar forms? Sounds like a flawed design.
 
L

Larry Linson

Rick, I appreciate the unwarranted criticizm.
I didn't say they were similar forms, and
they are not. This reply was not helpful.
Please refrain from helping me further.

That kind of response is a really good way to ensure that quite a lot of
people will "refrain from helping you further" -- none of us want to be
chewed out for trying to assist, and, from observing Rick B's previous
posts, I am certain that was his intent. However, unless he is much more
patient than most of us, I would wager that he will, indeed, "refrain from
helping you further."

I am not sure of all the modifications you describe. Generally, the only
things I can think of that would differ between Forms would be the name of
the Form and the WhereCondition in the DoCmd.OpenForm statement -- and
those, by necessity, would have to be manually changed.

The free MZTOOLS V3 for VB6 and VBA, from http://www.mztools.com, has a
feature to allow Copy and Paste Controls with Code, and to Rename Controls
with Code. You'll still have to change the name of the Form and the
WhereCondition argument in the DoCmd.OpenForm. I use other of MZTOOLs
features, too, and find it very useful.

Larry Linson
Microsoft Access MVP
 
N

NES

Larry, I understand. I too have posted in this forum before, and all replies,
including mine have been civil. I asked a reasonable question about copying a
button with code, and I got what very much sounded like a put down.

Please understand that I have been writing computer code since 1975. I've
written hundreds of applications, including a relational database from
scratch (without a database engine). And I have been commended by many,
including internationally, on my applications. One appeared in a scientific
paper (including screen shots) written by a physician at the Royal Brompton
Hospital in London. I am not a newbie. Access has a wealth of functionality
built in to it, and no one can know it all.

Rick's reply did not address the question at all. Had he done so along with
his criticism, I would have ignored the criticism. As it was presented, it
was simply a very public put down. I sincerely apologize to any and all,
including Rick, who may have been offended by my response to what appeared to
me to be an insult.

Thank you for bringing this to my attention, and thank you for your response.
Norm
 
R

Rick B

Norm:

My original post was quite short and obviously misunderstood. Had I taken
more time, I'm sure it would have come across better. I apologize for that.

Many many posts in here are from very new users who do not understand proper
design. Typically, when I see that a feature is going to be copied to 20
other forms, I assume that the user has built 20 identical or similar forms
instead of using filters or other features to make one form do what is
needed. A very typical example is that a new user will create one form for
each user of the database, rather than simply filtering the records in the
form to only apply to the current user. The developer then spends the rest
of their application's life making the same changes twenty times!

As your later post indicates, you are an experienced designer and you did
not indicate this was the case in your original post. It was simply a bad
assumption on my part. I tend to assume the worst design scenario when
reading posts in here. Unfortunately, that assumption pays off more often
than not :)

Hopefully you will get an answer that meets your needs. No offense taken
here. Hopefully none taken on your side either.
 
N

NES

Rick, I do understand, and I too apologize for being so quick to take offense.

Some of the forms are similar, but not all. Each form is based upon a
separate query that separates data based upon check boxes in each record
withing the data table. The table coordinates outside contractors,
organizations, government agencies, as well as internal employment
classification with association of internal departments for the purposes of
grouping (believe it or not) contact lists. There is considerable crossover
among these groups, and some require displaying totally different fields.
This is done to simplify contacting groups of people. It sounds complicated,
but the result, from a user standpoint is very easy to use with the
switchboard. The buttons allow the user to click on a record within a group
and immediately display the original input screen to view complete data or to
make changes.

I have taught newbies in the past, and each time I dread the thought that
someone will pickup a mouse by it's wire and ask "what's this for?"

Thanks for clarifying you response. There are no hard feelings here.
 
Top