Buy out EverythingAccess.com's vbWatchdog add-in and incorporate it into VBA
Error-handling: Buy out EverythingAccess.com's vbWatchdog add-in and incorporate it into VBA. It makes error-handling so much easier and much like that in .NET.
Washing the pussy would be great so it don't smell like ass ami adams
Would LOVE a better find/replace. My personal favorite was Speed Ferret (which only works with Access 2002? or earlier, not 2003 or any of the .accdb formats).
Has anyone ever compared Rick Fisher's Find and replace to the find and replace in the VBE?
If you had then you would have noticed that F&R is noticeably slower.
So to employ a third party product to do what MS can do internally, at a lower level that is much faster, would not be the most effective solution
But where would we be without F&R? Totally invaluable.
So yes, I agree that MS should include this functionality in Access, but MS should write this from scratch.
Klaus Oberdalhoff commented
Hi George, well, that is generally OK, but that two points: a) vbWatchdoc (EverythingAccess) b) Find & Replace (Rick Fisher) are points, which should be in the product as a valid standard. I find it ashaming for a product (or the team behind), if you still have no possibility to search & replace all over the database or you not even can search & replace within the SQL-Code of the SQL-editor (the team could just replace the sql-editor with notepad) or if you don't get the function or module name of the current function ... And I find it a good idea if you suggest to buy that two tools and incorporate them into the product (which is much faster and needs less development and testing time)
[Deleted User] commented
Valid point George.
George Moore commented
Perhaps we're being too literal here (occupational hazard?). I don't think anyone is reallly pimping any products, but perhaps illustrating their suggestions with "like the program that so-and-so has already made".
The theme here is offering suggestions for improvement, not evaluating someone else's suggestion on behalf of Microsoft or questioning motives.
Moreover, if I were one of the very smart people who came up with a desirable add-in program - and knowing MS's propensity for buying other companies and incorporating their technologies and methods - I'd be flattered to have MS make an offer I couldn't refuse. Why sell/support a $29 piece of software for the rest of my life when MS is standing at my door with a large check today?
I, for one, am always happy to see references to other utility applications/sources and have purchased a number of Access add-in programs I may not have otherwise found. It's an interesting world, and there are plenty of smart people I can learn from.
[Deleted User] commented
Same idea as https://access.uservoice.com/forums/319956-access-desktop/suggestions/14833125-buy-fishers-find-and-replace-and-incorporate-it . Make real suggestions for features, rather than buy this, ... Say we need a better Find and Replace Utility that work throughout the entire databse, .... Say, improve VBE/VBA to enable better error reporting to automatically include Module Name, Procedure Name, Line Number instead of buy this....
Considering the level of engagement MS has put forth on this site's suggestions, I wouldn't hold my breath on this one!
Grover Park George commented
At the risk of throwing fuel on the fire, I want to speculate what might be said about Microsoft if they went about buying up all of the smaller, independent software companies and putting them out of business. I think that is often called "monopolizing" and is generally frowned on.
Frank Rotolo commented
Are we now using this site to peddle other people's products?.. Someone else suggested MS buy or license Rick Fisher's "Find and Replace". I'm waiting to see if someone suggests to buy Luke Chong's FMS..
Not to be pessimistic, but this is probably not going to happen ...
RE: "the number of the codeline that produces the error would be very useful"
MZTools, among MANY other thihgs ... does Line Numbering. Then, you can use the ERL function in your error tapping / Message Box to display the Line Number of the Error.
Alan Cossey commented
That's all part of vbWatchdog and, no, I have no connection with them apart from using their product(s).
the number of the codeline that produces the error would be very useful