Comments for BKeeney Briefs

Comment on ARBP New Year New Changes by scott

scott — Tue, 07 Feb 2012 02:33:11 +0000

I know we can use your help. Please volunteer if you are inclined to help.

-scott

Comment on Dear Idiotic Developer by Bob Keeney

Bob Keeney — Mon, 06 Feb 2012 15:00:32 +0000

Beatrix Willius :
@jjb

Forgot a good one: Having the same information twice in local and global variables and working with both type of variables. It took me some weeks of getting this out of the complete application. Since then I know why globals should be prefixed.

Ouch.

Comment on Recordset.idxField vs Recordset.Field by Mark Dolan

Mark Dolan — Mon, 06 Feb 2012 13:40:36 +0000

I never have a need for speed in database client applications, the number of transactions per second is usually less than 1 so I use Field rather than IdxField unless there’s an absolute reason not to (e.g. a generic support function where the column names my not be known in advance). Incidentally I did some work on an OPC project where the developer had used nested loops to cycle through two large recordsets, perform comparisons then update one of the recordsets… speed could have been an issue here … except that the whole thing could easily have been accomplished with a single sql statement executed on the server …

Comment on Dear Idiotic Developer by Beatrix Willius

Beatrix Willius — Mon, 06 Feb 2012 06:43:16 +0000

@jjb A very fond wish that most likely you won't get. Forgot a good one: Having the same information twice in local and global variables and working with both type of variables. It took me some weeks of getting this out of the complete application. Since then I know why globals should be prefixed.

Comment on Dear Idiotic Developer by jjb

jjb — Sun, 05 Feb 2012 20:36:45 +0000

Nobody ever gets to see my code…

Comment on Dear Idiotic Developer by Bob Keeney

Bob Keeney — Sun, 05 Feb 2012 16:57:39 +0000

@Paul Lefebvre That's a good one, Paul. I've looked a few projects where every variable was a global variable. The guy had NO local variables in any method and he wondered why he was getting odd behavior when multiple windows were open.

Comment on Recordset.idxField vs Recordset.Field by Allan Berger

Allan Berger — Sun, 05 Feb 2012 04:34:20 +0000

Thanks for the speed testing! I flip back-and-forth depending on my mood – having started with .idxfield from the early examples. Now I have a reason for choosing one or the other.

Comment on Dear Idiotic Developer by Paul Lefebvre

Paul Lefebvre — Sun, 05 Feb 2012 00:45:01 +0000

I had a project that was to migrate a VB.NET app to Real Studio. When I got the code and opened it in VS, I only found a few objects in the Project List. I opened what was the main window and it took VS over a minute to display the window.

The entire application had all its code in this one window! Thousands and thousands of lines of code. Methods were hundreds of lines long or longer. Everything was stored in global variables and code was copy/pasted all over the place with no code re-use.

I told the client that if I were to take the project, I would not migrate one line of his code. It was too bad and that everything would be re-written in Real Studio based on how the app worked, not its original code. He agreed, although I’ve still had to go back and refer to the original code a few times.

Comment on Recordset.idxField vs Recordset.Field by Bob Keeney

Bob Keeney — Sat, 04 Feb 2012 23:34:01 +0000

@Stephane idxField has its uses and you're right that generic database code makes it mandatory. But next time someone says the idxField is far better/faster we all know better now.

Comment on Recordset.idxField vs Recordset.Field by Bob Keeney

Bob Keeney — Sat, 04 Feb 2012 23:32:16 +0000

@S-Copinger In either case, the IDE does NOTHING to help you eliminate errors like that. It's one of the reasons why we use ActiveRecord on a lot of projects because once it's all set up it's uses dot notation and autocomplete works for Table and field names. So absolutely no issues with typos or using the wrong data type.