Mark A Matte
markamatte at hotmail.com
Sat Jul 20 01:32:53 CDT 2013
Hello All, I'll preface with 'JUST FOR LAUGHS/SMILES' ...but could this be considered the pre-game show for a re-make of the "Great Debate of 1999, '02, and maybe '04...Bound vs. Unbound"? I know I have not be an active participant for some time...but I and appreciate everyone here...and what the group represents. Thanks, Mark A. Matte > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Tony Septav > Sent: July-05-13 10:44 AM > To: 'Access Developers discussion and problem solving' > Subject: [AccessD] Crap 2 > > Hey Jim > Correct on all points. If we all submitted an application for critique by > members on this list, we would get smacked, whacked and in some instances > trashed for why we had done things the way we did. My feeling still is if > your program is clean, stable and smart and it works the way the client > requested then you have done your job. I love to read the way others > approach a problem on this list and many times I go back and rethink my > code. But again their really is no right or wrong way of doing things. > If it takes 3 lines of code vs 20 lines of code really who cares, in the end > if your program is 99% bullet prove then again you have done your job. > > Tony Septav > Nanaimo, BC > Canada > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman > Sent: July-05-13 9:59 AM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] VBA Field Names - Curiosity Question > > Tony/Darryl/Rocky, > > While that's all true to a point, an app can work as intended and be > stable, but still may be problematic. > > It may be a royal pain to maintain, or may not be as fast or efficient if > someone else had written it. So what other developers/programmers feel is > right and wrong and *why* is important to me, because if I can do a better > job then I'm doing, I owe that to a client. Plus I never know when someone > is going to pick up a piece of my work and judge me by it. > > So in the end, other peoples viewpoints are certainly worth while to look > at. > > Caring about what others in your field think is what separates the > hobbyists from the professionals. > > Jim. > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin > Sent: Friday, July 05, 2013 12:15 AM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] VBA Field Names - Curiosity Question > > "A good program is one that works" > > R > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins > Sent: Thursday, July 04, 2013 5:19 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] VBA Field Names - Curiosity Question > > I feel you are right on point here Tony. If the client is delighted and the > app stable - than you have a win regardless of coding semantics. > > That is my feeling on the topic anyway. > > Cheers > Darryl. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Tony Septav > Sent: Friday, 5 July 2013 6:00 AM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] VBA Field Names - Curiosity Question > > Hey All > Cut the crap. > Who cares what each of us thinks is right or wrong. If you produce a good > product which you should be doing as a programmer and it is clean and works > the way the client has asked (now I have seen some others pretty S... code, > not on this list) you have done your job. Who cares how other programmers do > their job. Yes I have looked back at my code and thought "Hey I could do > this better". You deliver the product and smile as A,B and C have been > completed and you have done your job done as a professional. Sorry to the > newbies. > > Tony Septav > Nanaimo, BC > Canada > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman > Sent: July-04-13 9:43 AM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] VBA Field Names - Curiosity Question > > > Since I moved away from mini-computers back in the 80's, I haven't used it > except it for one occasion. > > It was for a Bill of Material explosion routine and the choice was use a > goto to loop back up to the top of the procedure or call it recursively. > > I chose the goto because it was clear what was being done, it was faster > because nothing went on the stack, and it was less resource intensive > because I didn't have to declare my level array as static. > > Jim. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan > Sent: Wednesday, July 03, 2013 07:12 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] VBA Field Names - Curiosity Question > > Correction: > > I haven't actually used a GOTO, other than in ON ERROR GOTO, for ... > > :-) > > -- > Stuart > > On 3 Jul 2013 at 15:30, David McAfee wrote: > > > On Error GoTo MyProcedure_Error ;) > > > > > > > > On Wed, Jul 3, 2013 at 3:24 PM, Stuart McLachlan > <stuart at lexacorp.com.pg>wrote: > > > > > Agree, what is the "danger of globals" if you: > > > > > > a. identify them properly using a naming convention b. use them > > > properly by only writing them in one location and c. trap errors > > > properly. > > > > > > Same with Goto. It's a perfectly valid command which does exactly > > > the same as the heavily used assembler JMP,JNE etc instructions. > > > > > > It's "abuse", not "use" that have given these two their bad reputations. > > > > > > (But I haven't actually used a GOTO for many, many years - I've > > > never found a situation yet where there wasn't a "more elegant" > > > solution <g>) > > > > > > -- > > > Stuart > > > > > > On 3 Jul 2013 at 9:04, Jim Dettman wrote: > > > > > > > <<And don't get me started on the danger of globals.>> > > > > > > > > I've used globals since day 1 with Access; have never had a problem. > > > > > > > > It's sloppy programmers that write sloppy code that's the issue. > > > There's > > > > nothing inherently wrong with globals from my viewpoint. They serve > a > > > > purpose and like anything they work fine when used properly. > > > > > > > > It's like the age old admonishment never to use a goto statement. > You > > > > can use goto to your hearts content and still maintain well > > > > structured > > > code. > > > > It's a sloppy programmer that ends up with spaghetti code. > > > > > > > > Jim.