You're trying to solve your political problems with technical
solutions to specific incompetencies on the part of your current
"developer". Continuing to come back to these newsgroups to
compensate for someone else's "sins" is a departure from the purpose
of them. We try to help the *developer* with technical issues to
resolve those particular issues - one issue per thread.

You are coming back for a "bank shot", If it is gratified I suspect
that there will be others...

I suggest that you try a different approach: At those meetings loudly
propose that the developer in trouble visit the list of Access
newsgroups that you provide him on the spot. I'd follow that up with
an email that lists at least this newsgroup and as many others as you
like. Just about any technical issue with Access can be resolved by
some responder here. Alternatively, the developer might discover that
what s/he wants to do can't be done with Access.

If you can determine the signature that the developer uses in the
newsgroups then you can monitor what is actually asked and the
responses received.

To resolve the political issues you have to use the tools at hand to
resolve them at the political level. Here's something scary to
consider; while it's not a given, people who are totally incompetent
using the higher level tools provided by Access usually haven't
bothered to learn about Relational Database Management Systems. That
implies that the schema on which s/he is trying to build functionality
is incorrect. If s/he asks questions that are particularly jarring
there will be requests for his schema to be included in a response.
It's my guess that his schema is badly flawed and that his thread will
end with no response. A very pertinent question to ask in a meeting
or via email is: "Is our database normalized to at least 3rd Normal
Form"? A qualified "Yes" might be sufficient. There are instances
where 3NF is departed for good reason. S/he should at least know what
it means.

Here is a burning question: Are you that developer? If so, come out
from behind cover and post your issues directly. We're not the Access
cops.

If and when you post back, please include a paragraph or two
explaining what your application is all about, Also, list your
schema: all of your table names and the names and datatypes of every
field in each table.

In addition you may send a zip file to my address that has the
application description and a populated copy of your application in
Access 2003 or earlier. I can look it over and give you some feedback
not just on the schema but on the higher levels of functionality as
well. I'll treat your data as confidential,

HTH
--
-Larry-
--

"jpwgh via AccessMonster.com" u39688@uwe wrote in message
news:7ef3d88ee18c4@uwe...
I wrote in Dec. 07 regarding a consultant with suspect programming
skills
(majority of programming done with macros and multiple examples of
empty code)
I appreciate all the feedback. The consensus was that he was
lacking some
skills (one even said to "fire his *ss"). Problem is we are stuck
with him.
For political reasons I can not bring up any issues about
questionable
programming or the way he is doing something. I can only make
requests about
how we want things to work. Even then, we are limited by his
abilities. I
made a request for something, but he can't do it. Since I can't
comment
about anything else, it sure would be nice at the next meeting to
tell him
how to do it. The problem:

After logging in, you go to a client search form (continuous form
lists all
clients). To add a new client, you click on a button to go to the
form to
add the new information. On close, you go back to the client search
form
(which was never closed). From here, there are one of two places to
go.
Problem is, to go to the next form, you must be at the record of the
person
you just added. His answer is to do a search using the search
button. I
would like to be at the record of the person you just added.

I was able to accomplish it in a small database I created using the
following:


Dim hldId
hldId = Me!Bed
Me.Requery
Me.Recordset.FindFirst "Bed=" & hldId

My scenario is similar, but my design concept is different. I am a
novice
and this is all over my head. I got the above code from a tech
site. I
search sites and tried different code. Nothing worked. Most of the
code I
found pertained to tables, not forms. Since my skills are also
limited (but
I don't pretend to be more), I am unable to adapt code to fit this
example.

Please!!!!!! Can someone help me? It will make going to meetings
with him
tolerable and maybe he will think twice before giving us bogus
explanations
and excuses.

Thank you for your consideration and any feedback

--
Message posted via AccessMonster.com

http://www.accessmonster.com/Uwe/For...esign/200801/1