OT How much knowledge is enough?

[salad]

If one looks at job listings one will read the requirements of for it;
..Net, SQL, C#, etc.

How much skill, if years experience in the discipline isn't listed, is
needed. Could one simply get the C# program, read a book on it, do a
"Hello World" program, and feel comfortable on the topic and apply for
the job?

How much knowlecge is enough, if you've got a developer background, on a
new language or subject to go for it?

[Lyle Fairfield]

CD********@Fort uneJames.com wrote in
news:11******** **************@ m73g2000cwd.goo glegroups.com:

Lyle Fairfield wrote:

>"Larry Linson" <bo*****@localh ost.notwrote in
news:3GtCg.423 64$gU4.39878@tr nddc07:

I have a colleague who occasionally hires subcontractors to do
Access work. He invariably includes as one of his "do-or-die"
questions: "How do you pass information to a Form that you open
with DoCmd.OpenForm? " or "What is OpenArgs?"

I haven't used OpenArgs for many years and I wouldn't suggest that
it's the way I would pass information to a Form that I open.

I would open the form with
Form_FormName. WhateverPropert y = WhateverInforma tion
or if there were mucho stuff to pass I would set a reference to a new
instance of the form.

I guess this explains why I am unemployed.

--
Lyle Fairfield

I've forgotten how to create an option group. I use code because it
gives me more flexibility. I haven't created an option group in
years. I'd probably fail a similar shibboleth. But I'm still employed
in spite of such an egregious lacuna.

I have not forgotten how to create an option group. This does not mean that
I know how to create an option group.

--
Lyle Fairfield

[David W. Fenton]

"Larry Linson" <bo*****@localh ost.notwrote in
news:3GtCg.4236 4$gU4.39878@trn ddc07:

I have a colleague who occasionally hires subcontractors to do
Access work. He invariably includes as one of his "do-or-die"
questions: "How do you pass information to a Form that you open
with DoCmd.OpenForm? " or "What is OpenArgs?"

I don't know his "percentage score" today, but he used to
eliminate well over half the applicants on that question alone --
figured if they didn't know that, they weren't "Access
developers."

I would assume he'd accept any answer that worked? I would never use
OpenArg myself -- I'd tend to use a class module, or design the form
so that it didn't need to know anything about the context in which
it was being used.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[David W. Fenton]

Lyle Fairfield <ly***********@ aim.comwrote in
news:Xn******** *************** **********@216. 221.81.119:

"Larry Linson" <bo*****@localh ost.notwrote in
news:3GtCg.4236 4$gU4.39878@trn ddc07:

>I have a colleague who occasionally hires subcontractors to do
Access work. He invariably includes as one of his "do-or-die"
questions: "How do you pass information to a Form that you open
with DoCmd.OpenForm? " or "What is OpenArgs?"

I haven't used OpenArgs for many years and I wouldn't suggest that
it's the way I would pass information to a Form that I open.

I would open the form with
Form_FormName.W hateverProperty = WhateverInforma tion
or if there were mucho stuff to pass I would set a reference to a
new instance of the form.

That would work, I suppose, for forms not opened modally, but if the
form is modal, it would have to have the information set up for it
before it opens.

I tend to use class modules as data storage structures for this
purpose, but one could use any number of structures for the same
purpose. I hardly ever use OpenArgs for this purpose in my recent
work (i.e., in the last 5 years).

I guess this explains why I am unemployed.

It all depends on what the person asking the question expects as an
answer. I'd give OpenArgs as a possibility for the very simplest
circumstances, but would allow that if you need to pass more than
one parameter, you end up having to parse the string you've passed
in and then it becomes pretty ugly, so at that point I'd go to some
kind of independent data structure.

Of course, I also have a preference for passing *no* information at
all to dialog forms, since so many of them that I use need to be
used in multiple contexts, so that's the ideal, a form that doesn't
have to know anything at all about anything outside itself. But, of
course, that's not always possible.

But that's the kind of answer I'd given.

If it would get me tossed from the job, I wouldn't want to work for
the guy, because anyone who wouldn't consider that kind of answer to
be sufficiently detailed is not someone I'd want to work for.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Lyle Fairfield]

"David W. Fenton" <XX*******@dfen ton.com.invalid wrote in
news:Xn******** *************** ***********@127 .0.0.1:

That would work, I suppose, for forms not opened modally, but if the
form is modal, it would have to have the information set up for it
before it opens.

This is not so:

The form code is:
****
Dim mBlah As String

Public Property Let Blah(ByVal vBlah As String)
mBlah = vBlah
End Property

Private Sub Command10_Click ()
MsgBox mBlah
End Sub
****

The code to open the form is:

Public Sub OpenForm1()
With Form_form1
.Visible = True
.Blah = "Wrong"
End With
End Sub

That is it opens and when one clicks Command10 the message box

When the form is modal it displays:

---------------------------
Microsoft Office Access
---------------------------
True / Wrong
---------------------------
OK
---------------------------

****

When the form is not modal it displays:

---------------------------
Microsoft Office Access
---------------------------
False / Wrong
---------------------------
OK
---------------------------

****

It works exactly the same whether or not the form is modal.

--
Lyle Fairfield

[CDMAPoster]

Lyle Fairfield wrote:

I have not forgotten how to create an option group. This does not mean that
I know how to create an option group.

--
Lyle Fairfield

Good one. I guess how much knowledge is enough is in the eye of the
beholder unless it's skin-deep :-).

James A. Fortune
CD********@Fort uneJames.com

[Nick 'The database Guy']

lol larry
Larry Linson wrote:

<ch************ @gmail.comwrote

Also, keep in mind, most companies
will have a candidate interview with
peers to ensure knowledge. The kind
of questions that come up will not
be how to make a "Hello World" type
application, but more in depth than
that. I usually present an actual problem
that I'm having to see how the candidate
responds.

I have a colleague who occasionally hires subcontractors to do Access work.
He invariably includes as one of his "do-or-die" questions: "How do you
pass information to a Form that you open with DoCmd.OpenForm? " or "What is
OpenArgs?"

I don't know his "percentage score" today, but he used to eliminate well
over half the applicants on that question alone -- figured if they didn't
know that, they weren't "Access developers."

Larry

[Larry Linson]

"Lyle Fairfield" <ly***********@ aim.comwrote

I guess this explains why I am unemployed.

Possibly, if you sought subcontract work from my colleague. <GRIN>

What is the advantage of creating and using a custom property to pass
information, versus using the supplied-with-the-product, builtin OpenArgs
property?

Larry

[Lyle Fairfield]

Larry Linson wrote:

"Lyle Fairfield" <ly***********@ aim.comwrote

I guess this explains why I am unemployed.

Possibly, if you sought subcontract work from my colleague. <GRIN>

What is the advantage of creating and using a custom property to pass
information, versus using the supplied-with-the-product, builtin OpenArgs
property?

At one time I was considering offering a colleague of ours some
work/partnership on a project of mine, giving him USA rights,
responsiblity, as an alternative way to his making a living if he were
to stop doing something I (we) didn't like (Sort of an atheist doing
what Jesus would do). I was dissuaded by someone else involved; when I
see some of his exaggerations here, especially his attempts to belittle
you, I shudder at what he might have made of that.

As to using "my" method:

It's consistent with how we deal with all objects?
Its syntax is identical for both forms and subforms?
Its syntax is simpler, and of course there is no parsing the passed
argument string or type casting its various parts.
Of course, one is likely to use built in properties
Form_Form1.Capt ion = "Don't Screw it Up Again, Please!"
Form_Form2.Allo wEditing=False

[David W. Fenton]

"Larry Linson" <bo*****@localh ost.notwrote in
news:vCSCg.8609 4$Lh4.31865@trn ddc02:

"Lyle Fairfield" <ly***********@ aim.comwrote

I guess this explains why I am unemployed.

Possibly, if you sought subcontract work from my colleague. <GRIN>

What is the advantage of creating and using a custom property to
pass information, versus using the supplied-with-the-product,
builtin OpenArgs property?

Well, for one, it makes it much neater to pass multiple values.
Second, by setting the values themselves, you can trigger actions
based on those (just as you can in any class module custom
property).

But the drawback of that approach is that it's limited to forms not
opened modally. I don't have too many of those, so I use standalone
data structures for passing information.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Lyle Fairfield]

"David W. Fenton" <XX*******@dfen ton.com.invalid wrote in
news:Xn******** *************** ***********@127 .0.0.1:

But the drawback of that approach is that it's limited to forms not
opened modally.

I think this is not so, as I previously explained.

--
Lyle Fairfield