hi
Mick,
It will be an open code project and free for all
wonderful!!!
One reason I don't like ACCDE's is that they protect the code so its NOT open. It is in the best interest of all of us who love Access, and want to keep it thriving as a product, to help other developers build more successful databases. That will do a lot to change the bad reputation that Access has gotten since now the marketing materials say you can build a quick and easy application in a few minutes so, essentially, with no real knowledge -- which just ain't true! Sadly, those bad databases with lots of problems, are often created by consultants who charge for them and then protect that bad design, which further enforces the bad press. Its also sad when some take what we freely share and commercialize it -- luckily they are few ... but some of them have deep pockets, bash our free tools, and manage to convince others that they shouldn't even try them. Despite that, I'll continue to be who I am.
I know there's a line one needs to draw ... and I fail to do that by giving so much away, which also keeps me mostly broke! ... but being successful, to me, isn't measured by a bank account. Its great when people donate, even just a little when they benefit from a tool. Every little bit says "thank you" and inspires. Then we can continue to freely share with all, as we inherently want to do!
15 years since I built a addin but have yours as an example
thanks. Building add-ins is a poorly documented topic! I stumbled myself, and want to save others from those same pitfalls stemming from a lack of documentation. Watch the video I linked to as well -- there is a list at the end of the things you should set. Not everything an Add-in reads is in the usysRegInfo table -- some are database properties.
I was thinking of doing that as well as they would work better together I would send each line not starting with ' and run the key words on that line returning the formatted line back to add to the end of the string.
That way to find a comment isn't good enough -- a comment could be at the end of a line (and words in the comment could be keywords!), or a single quote could be somewhere in a statement, inside double quotes. I think the trick, which I didn't do before but will do now, is to find the comment first. Then only mark keywords before that position.