Search results

@Gasman I know you are done :cry: but the latest version has chapters now. If you have any comments on the new format I'd be all ears.

I was around before windows, and back then DOS was the "ultimate framework". In the end it is really about the bios handling the very low level stuff, disks, serial ports, interrupts, memory managemt (at the very basic level) and then building up on that to give us devs hard drives, displays...

LOL. And yea and all of the Linux folks are squirming... Really I was just using that as an example of the framework taken to the extreme. I was around before windows, and back then DOS was the "ultimate framework". In the end it is really about the bios handling the very low level stuff...

This is true. I have done work in Excel, Word, Access and Outlook. The biggest issue there is that the environment is completely different from Access. We really do have the "best" environment for easily and quickly writing code. And also re where the code is stored. In a worksheet...

"the color element failed" - No, color was the name of an open arg passed in, with an associated color value. I used "Color" Intentionally, knowing that it was not going to work as a property of the form. Form's don't have a color property, at least that I can find with an OpenArg named...

I might be reading too much tone into your statements. I am just trying to make you aware of how I hear you sometimes. If I hear tone do others too? You are a very knowledgeable and helpful guy, and thinking about how you might sound may make you more approachable to some of us. I do want...

Sorry but this is so far away from whatever we were discussing that I am totally lost. As for colors... I normally just use the vbCyan kind thing. Why it is not that is lost in the mists of an overly long thread about things totally unrelated to the original subject.

@MajP Thanks for the links to the subject. The pearson software link is good but basic. I will say that I created a Locals window docked next to and on the right of the debug window. I do not even bother clicking off to anything for Excel developers. If I am going to be reading in...

@dalski the actual live PDF can be found here: EventDrivenProgrammingInVBA.pdf And yes, I have been accused of writing like a drunken fireman spraying water from a firehose. Please do download that and please store a reference to the book somewhere. I have a saved page reference in my...

@MajP - I do not get it. This is standard debugging, Is OffPutting. It gives you an "I'm superior because" sound. Folks come in all shapes and sizes and what is "standard" to you has never even been looked at by others. Access is hugely complex, just learning about the non-vba side of...

@Edgar_ I like it! I mean I REALLY like it. I have done this a bit, but not to the level I should . Having said that, would you consider starting a separate thread for this. "Debug tools, how to debug our code" or something like that. This post is buried deep down in a thread which really...

@dalski And thank you for reading and commenting on it. I will go look at page 28 and fix it. As you may have discovered, the book PDF is live out on GitHub. But can you cut and past a small bit of the text into here so I can search for and find it? I have switched from .odt to .Fodt, which...

I just went through MZ Tools and didn't see anything like this.

B But I have no idea what these tools even are. I use MZ-Tools, and have for decades. I would absolutely love something that scanned code and said "This might need to be manually set to null". I believe I have rubber duck too but don't actively use it. OTOH I don't actively develop any more.

LOL. So go start a thread about debugging tools. We need that! It sounds very "I'm superior because..."

And I absolutely understand and agree with you. That said... the novice programmer comes in and someone says... don't worry about it, the "garbage collector will clean it up.". And you know what, that is true because they are not doing anything complex. And now they have learned they don't...

The issue with this is that it does take a lot of experience, which you absolutely have (but the novice absolutely does not have), to actually know when it will cause an issue and when it won't and if you get it wrong things do not work right, and trying to figure out why things are not working...

And I have never done so. I just pay absolutely no attention to its value. Its only use in my universe is as a unique record identifier, to be used as a foreign key in a child table. In 32 bit Office, an autonumber is a 32 bit number.It can have 4 294 967 296 possible positive values...

And THAT was cool! :cool:

It is indeed poor practice. The autonumber is supposed to be just a surrogate Key.