Quote Originally Posted by Elroy View Post
The DAO360.dll isn't intrinsically part of VB6, but it too has been pre-installed with the Windows OS since Windows XP. If Windows has been installed correctly, it should just "be there", all registered and ready to use.


Therefore, if you stick with the intrinsic controls and DAO 3.6, you'll have no need for an installer. Your VB6 compiled EXE should be completely portable (excluding any other custom data files your code needs).
This ^^^^^. I used to not mind writing an installer, but for the last few years I've gone to great length to keep my applications portable so that they can run directly from a portable storage device if needed.

Another consideration is where to store application settings and such. I was using custom settings files which were created by my programs and located in the application folder but that resulted in settings files sometimes appearing in unwanted places such as the desktop and so I recently moved to using a standard INI file which is stored in the user's app settings folder on the target machine.