Hi,



Dunno if anyone can help - I am looking at turning my hand to Access 

Development and would like to know what kind of standard is required or 

expected. I have already developed several db's and everyone has seemed 

happy with them, however really I need to know if I am exceeding 

expectation (I like to exceed by only by a little!) or not. Generally I 

have approached the development as a non-developer and hence the client is 

going to be happy no matter what!

Would anyone know of anywhere where I can view examples or sample db's, in 

order to see if I am up to scratch or not?



Cheers... 

Lee Hambly.

In my humble opinion, there is no real measure.  If you can do what the

client needs than you are up to scratch for that job.  If you can't, you

need need to work to improve yourself.



-----Original Message-----

From: leehambly@y... [mailto:leehambly@y...]

Sent: Wednesday, December 12, 2001 7:41 AM

To: Access

Subject: [access] Examples





Hi,



Dunno if anyone can help - I am looking at turning my hand to Access

Development and would like to know what kind of standard is required or

expected. I have already developed several db's and everyone has seemed

happy with them, however really I need to know if I am exceeding

expectation (I like to exceed by only by a little!) or not. Generally I

have approached the development as a non-developer and hence the client

is

going to be happy no matter what!

Would anyone know of anywhere where I can view examples or sample db's,

in

order to see if I am up to scratch or not?



Cheers...

Lee Hambly.

<< In my humble opinion, there is no real measure.  If you can do what the 

client needs than you are up to scratch for that job. >>



Hmmm... I would have to agree only in part with that statement.  Giving 

the client what it needs is a good start.  However, you need certain 

skills in place to make sure you give what the client needs and it's not 

going to cause problems in the future.



For example, in my office is such a person who "gives the client what it 

needs."  Most people do not trust this individual when they are told what 

exactly is "under the hood" of his programs.  His programmng style is 

sloppy, he rarely to never adds comments to his code, and he bypasses or 

even de-programs Windows standards in his forms (e.g. making people double-

click a form element that other "standard" Windows programs require a 

single-click, and vice-versa).



"If it works, why is that a problem?"  Because mostly likely, someone is 

going to inherit this database in the future.  I guarantee you it'll be a 

nightmare for the person to unscramble what was done to "upgrade" or debug 

this inherited database.



To answer the original question, IMHO you need four characteristics:



1) strong programming skills,

2) understanding of database elements and structuring,

3) a good, logical, analytical mind with eye to detail,

4) knowledge of what people are doing "out there" as far as efficient 

programming standards and techniques.  That includes joining a forum like 

this one.



With these you can master almost anything.  For database examples, install 

all of Access's samples and look at them.  Also, find others who create 

and maintain databases similar to what you're going to author and look 

closely at them as well.



Good luck!



Greg

Touche, Gregory.  You are correct.  I am currently supporting several

programs that were built by predecessors of mine that are poor quality,

but do what the client wants.  However, this is more a rating of the

product than the programmer.  The high ability of the programmers that

did the work in those program is evident.  It wasn't that they couldn't

do better, it was that they didn't do better.  I merely meant that the

necessary skills to be a programmer depend on the job.  I know

programmers that do well in their job, but if they were to come to my

position they would not do well because their skill levels are too low

for my particular job.



I would add to your list:

5) a good work ethic (willing to put an extra few minutes to make it

more readable, etc.)

6) an eye for future planning.  (building a program for these exact

requirements is nice, but a good programmer should try to make their

programs flexible enough that they don't fall apart on minute changes).



Yehuda



-----Original Message-----

From: Gregory Serrano [mailto:SerranoG@m...]

Sent: Wednesday, December 12, 2001 1:20 PM

To: Access

Subject: [access] RE: Examples





<< In my humble opinion, there is no real measure.  If you can do what

the

client needs than you are up to scratch for that job. >>



Hmmm... I would have to agree only in part with that statement.  Giving

the client what it needs is a good start.  However, you need certain

skills in place to make sure you give what the client needs and it's not



going to cause problems in the future.



For example, in my office is such a person who "gives the client what it



needs."  Most people do not trust this individual when they are told

what

exactly is "under the hood" of his programs.  His programmng style is

sloppy, he rarely to never adds comments to his code, and he bypasses or



even de-programs Windows standards in his forms (e.g. making people

double- click a form element that other "standard" Windows programs

require a

single-click, and vice-versa).



"If it works, why is that a problem?"  Because mostly likely, someone is



going to inherit this database in the future.  I guarantee you it'll be

a

nightmare for the person to unscramble what was done to "upgrade" or

debug

this inherited database.



To answer the original question, IMHO you need four characteristics:



1) strong programming skills,

2) understanding of database elements and structuring,

3) a good, logical, analytical mind with eye to detail,

4) knowledge of what people are doing "out there" as far as efficient

programming standards and techniques.  That includes joining a forum

like

this one.



With these you can master almost anything.  For database examples,

install

all of Access's samples and look at them.  Also, find others who create

and maintain databases similar to what you're going to author and look

closely at them as well.



Good luck!



Greg