Andy Lacey
andy at minstersystems.co.uk
Thu Dec 2 03:25:13 CST 2004
Agree with every word Erwin. I only wish I could curb my tendency to lapse into using a short name when I'm coding something quickly. It's such a temptation. I always mean to do a find and replace once I've finished and change all ocurrences to a longer, more meaningful name, but I often forget. Well, good to get that off my chest. I feel quite shriven. -- Andy Lacey http://www.minstersystems.co.uk --------- Original Message -------- From: Access Developers discussion and problem solving <accessd at databaseadvisors.com> To: Access Developers discussion and problem solving <accessd at databaseadvisors.com> Subject: RE: [AccessD] code help please Date: 02/12/04 09:33 > > Yes that was it... > > I know that was a specific problem, but it is this problem that made me > decide to always use the full comparison in a if statement. It was also > advice in some access guru books for better readability. > I find myself pretty obsessed with writing easy to read and > understandable code. > > My variable name are, for instance, pretty long so it clear for what it > stands. > It will make my code longer but not slower... > Programming with long names does not really slow down develepmont thanks > to copy/paste technology, but also a more frequent use of enums, types > and classes. > > I dont know why, but I only (really) discovered the use of classes about > a year or two ago and I'm pretty fond on using them. I more work to > create them but I find the use afterwards far better and the code is > much more structured. > > But I'm way of topic here... > Erwin > > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Andy Lacey > Sent: Wednesday, December 01, 2004 1:43 PM > To: Access Developers discussion and problem solving > Subject: RE: [AccessD] code help please > > Better safe than sorry Erwin, I know, but if you're thinking of the > problem of Access not shutting down correctly then according to MS this > was a very specific problem: > > "You have code behind a subform control that references a Boolean > control such as a check box on the main form, and are using an If..Then > statement to implicitly test for a value of True, as shown in the > following example: > > If Me.Parent![CheckBox] Then" > > See http://support.microsoft.com/default.aspx?scid=kb;en-us;190074 > > > -- > Andy Lacey > http://www.minstersystems.co.uk > > > > --------- Original Message -------- > From: Access Developers discussion and problem solving > <accessd at databaseadvisors.com> > To: Access Developers discussion and problem solving > <accessd at databaseadvisors.com> > Subject: RE: [AccessD] code help please > Date: 01/12/04 11:14 > > > > > I would prefer > > > > if isnull(me.txtPONptes) = true then > > > > I know there use to be a bug in one of the access versions with this > "if > > x then" without the "= y" part. > > They where wrongly interpreted due to this missing operator. > > Some Access books advice to write the full comparison for better > > readability and bla bla bla... > > > > > > > > > > > > > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Andy Lacey > > Sent: Wednesday, December 01, 2004 9:16 AM > > To: 'Access Developers discussion and problem solving' > > Subject: RE: [AccessD] code help please > > > > Joe > > > > if isnull(me.txtPONptes) then > > > > > > IsNull is a function. > > > > -- Andy Lacey > > http://www.minstersystems.co.uk > > > > > -----Original Message----- > > > From: accessd-bounces at databaseadvisors.com > > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Joe > > Hecht > Sent: 01 December 2004 07:47 > To: 'Access Developers > > discussion and problem solving'; 'ACCESS-L' > > > Subject: [AccessD] code help please > > > It is almost > > Midnight here > What is wrong with the following code please? > > > > > > Private Sub ReportFooter_Format(Cancel As Integer, FormatCount As > > > > Integer) > > > if isnull me.txtPONptes then < This is null line is the > > > trouble maker > > > Me.lblPONotes.Visible = False > > > Me.txtPONptes.Visible = False > > > End If > > > > > > End Sub > > > > > > JOE HECHT > > > LOS ANGELES CA > > > jmhla at earthlink.net > > > > > > > > > > > > -- > > > _______________________________________________ > > > AccessD mailing list > > > AccessD at databaseadvisors.com > > > http://databaseadvisors.com/mailman/listinfo/accessd > > > Website: http://www.databaseadvisors.com > > > > > > -- > > _______________________________________________ > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > -- > > _______________________________________________ > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > > > > > > > > > > > > > > ________________________________________________ > Message sent using UebiMiau 2.7.2 > > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > > > > ________________________________________________ Message sent using UebiMiau 2.7.2