Recent content by DickyP

One of the gotchas noted in the Reilly VBA book is that CInt() returns an integer, whereas Int() returns the integer of a number but as variant version of the original data type! Lots of scope for variations.

All the above shows is that my choice of using the Decimal datatype when doing this sort of arithmetic saves time and effort (and frustration). As I have said many time on Access World, If there is one thing that VBA truly needs it is a native decimal type rather than having to use the Variant...

As almost an aside the is probably no technical ambiguity -see above - but, however, there is mental ambiguity to the user in " what a I referring to this this time?"

To me using proper naming conventions is as important as proper code formatting and proper relational data design: if you've got them you are 99% of the way to successful development. I'm still using the Lezinski naming conventions I started using with Access2 and VB 3.

I actually generally use the Me.ControlName syntax - I merely offered the Me.controls("Name") as a possible choice, where necessary.

True but that is based on the bizarre suggestion you are going to use it for real without testing. If you do that you deserve everything you get.

If you want to guarantee that your references to a contro lis correct you can always use the  formname.Controls("controlname") form of notation.

As a footnote to my complaints about the National Lottery making minor, unpromulgated changes to their CSV results download files i thought I'd share my latest wheeze. The problem with the changes is that the necessitate commensurate changes in the Import Specs and hence a release of the FE...

For what it is worth I've always (at least since Access 97 which formally introduced classes), had a class which I call clsAppDetails, which I instantiate as ThisApp at Start Up holding all the data items I may want during a session. It may, or may not, been a sensible solution to Access...

The_doc_man has exlained very clearly my immediate reaction to this scenario: why is Access a problem? Answer it's not. Mind you I was thrown to start with by the use of the abbreviation PIV, as to me it refers to ventilation engineering!

I've never tried explaining to a cross-dresser, so I don't know :)

I'm assuming this is thread specific, because as a general statement it is far, far to sweeping.

Dunno - as far as I know I haven't yet been accused, at least not to my face, of mansplaining. I would say that I haven't noticed that men explain things differently to women than they do to men.

Mansplaining - a simple, normal explanation that annoys a female because she has to acknowledge that you know more than her on a particular topic.

My solution has been to save the historic data in the tables to XML, which is easily retrievable, when required.