GKatReliable
Programmer
I need to change my VB6 program to run in the wee hours of the morning on an unattended machine, probably through task scheduler. I want to know how to re-arrange my VB code. We are taught to create a form, put on a command button and write code behind that to do stuff, then put on another command button on the form to quit. Well, with no user interaction, where in my VB project does the code go so that it just plain runs, then gets out? This is a deal where the mainframe generates a download overnight, then this program pulls that in, reformats it, and stuffs it into an Access database on an internal Web server for our ASP code. Real work kinda stuff. Do you really need a form in VB? It used to be, back in simpler times before all this visual stuff, you just wrote a BAS program and compiled it, and it ran.