internet explorer - Excel VBA and InternetExplorer causing errors on website -


I have some "smart" users who have written an Excel spreadsheet that automates some of their tasks on our intranet / tile sheet . It seems that the example of a built-in Internet Explorer is not doing everything I expect of a browser, e.g. Set up Cookies Is there a way to find out if a user is killing a web site with Internet Explorer's VBA COM object instance? I can not keep users from making creative solutions but I want to handle them. Thank you

Some things come to mind first, until any restricted information or web scraping data If you do not intend to make public, it is better to fix the site so that the site works with purpose, but the user can still use VBA to access the place. VBA is an important productivity tool for many businesses and can provide people the flexibility to "extend" a site for those places which may not be suitable for development requests.

However, if you insist on trying to break your user's application :) ... check the dom window. Visual property is not a sure-fire, but an example of many web-scraper Internet Explorer "Roboting" can not be invisibly also that cookies are not being set, they are only being removed on the fly. . If you are trying to limit page-hits with cookies, then you should consider the basic truth that any data stored on the client side is subject to change. Instead try to store such information server-side. As mentioned earlier, some methods do not submit proper headers, so that you can check them, and in the end there is a popular "captcha". Of course, none of these methods is stupid and all this are lacking.

Everyone said, if one thing I have learned, then it is that people will find a way to do their job. You can lock your interface as much as you want, but if the user believes that whatever they are doing is necessary to do their job, they will find an alternative solution to implement your "applicable" Will be very motivated to. And they will probably earn praise and recognition for their efforts. The user will keep this as long as you do not meet their needs which they believe

If you really want to kill the app, then to recognize it It is better that the requirement is not being met, and to fulfill it. If managers do not want to managers to support and maintain 100 different small applications to do this. If there is a "legitimate" hassle-free way to fulfill the need, then how will it be used normally? Everyone is pressed for time, so simple solution wins. If you are trying to make your app better than any one, why bother with the development of the house? A business unit manager will direct his employees back to business if an excuse is given


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

jquery - SimpleModal Confirm fails to submit form -

php - Multiple Select with Explode: only returns the word "Array" -