Database management app

Project Description: Overview: Create Windows program that runs in the background and on start up on the client's computer that grabs CERTAIN data from [login to view URL] file (SQL ServerCE 3.5 File) and saves it on our web server. Create a second Windows program on our machine(s) that retrieves the data described above and ADDS it to the .SDF file (SQL ServerCE 3.5_File). Details of design: Three terms: 1) Client = client machine (Windows), 2) FTP = Web server, 3) Server = Our local machine(s) (Windows). The Windows program on the clients computer has an input for First Name, Last Name and Password and email address associated with it. Client can input this data on install or by accessing program from tray. The client SQL file will have data under the heading SIM101. This field will ultimately be changed to the client name and password in the following format (Last Name+FirstName+Password) on the Server machine. At the appropriate time(s)and if there is a change from the last time a file was written, Client uploads it to FTP (address as specified in an ftp file). Client program runs in the background and on startup on the client machine and otherwise requires no user management. There is a button for the client to hide it and there are controls in the tray to make it show or to exit. If new files are present, Server downloads client files and integrates them into SQLServer3.5CE DB. Only relevant data is transferred associated with the Sim101 key on Client and the data associated with that key is integrated into Server DB in the proper format but on the Server it is labeled with the above given client name instead of Sim101. Server control has an input for where the .SDF file is kept. Compression will be used if relevant. No FTP information can be viewed on Client machine. As mentioned, there is a file on FTP that specifies the ftp address and password for all clients. The above transfer will occur each day starting at the specified time(s). There is an server side file that specifies the interval and/or the end time (specified in Eastern Time). For example, the transfer may occur starting at 930 AM Eastern Time and additionally at 30 minute intervals until the end time which is the final upload for the day. If it seems the files are large which they probably will not be, then set the intervals to the user's log in time instead of clock intervals (i.e. 30 min after the hour). In order that clients do not all send files to FTP at the same time, the transfers can occur off a slightly random time on the client. There is never more than one file for each client on the ftp. Only the most recent, so old files will be removed. Further, the client will only send a file to ftp if there has been a change since the last file was written. On the server: If the file is found to be smaller than previous uploads, then a line is appended to a server side file that shows the date and time, Last Name+FirstName+Password, and the words "File is Smaller" On the Server: Scan the file nt_order column labeled "filled" for any values > a specified amount (default to 1). If any value in this column exceeds the default level then a line is appended to a server side file that shows the date and time, Last Name+FirstName+Password, email (live link) and the words "Contracts Exceeds Default of [+ Default Value]. The above may be done for any number of clients. For example we expect to be able to handle as many as 200 clients and ideally we will only have client send data once per day as specified in the FTP located file. This defaults to 1630 Eastern Time. The resulting SQL ServerCE 3.5_File on the Server machine will be organized in such a way that it can be read by NinjaTrader. NinjaTrader is the program that created the original files and is the program that will read the appended files. Client will use a Windows installer and will have a license we will provide in the installation procedure. Code will work on any windows machine.