OLAP TCP/Ip Client

This application wil be a small Proof of Concept (POC) that may lead to a large contract if I get the project. This POC is the client side of a typical TCP/IP client/server application. The user will need to be able to do a few things to prove the functionality of the product: -Login/Logout of the server. Save multiple servers in a list, select available servers from the list (available servers = servers that have been found by the client application to be active) Once Logged in: -Select two date ranges (this will have to be a slick UI that allows the user to select a 'This' and 'Last' timeframe either by day, week, or month, and select the starting ragnge and ending range of each date range. -Select from an available list of keys/dimensions to display -Make a Comparative request to the server, and display the results in a chart, sort of like Excel. The chart will have the ability to 'Drill' into a particular row of data to show a subset of that row. -Each row will have a second level of data that needs to be displayed if the user clicks once on the row, or a + sign next to the row. (sort of like a tree-view) -The user will need to be able to select from multiple columns of data, one or many columns to be displayed at once. -Several network requests will need to be made to the server to retrieve this information. -upon network drop, the client will detect and re-login with no user interaction The server is a fully functional server that is very mature. This will be a new client to this application. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). 4)All software as described above 5)Directions for installation and configuration of this software & the Windows PocketPC software. This will have to match functionality of an existing Fat Win 32 client. Screen Shots can be provided, and you will be able to login and utilize the Fat32 client if you need to. Since this is a POC of a large product (the original Fat32 client is about 10 years of consistant improvement with a team of 3 - 6 engineers) the winner will have the 'inside track' on the large project. ## Platform Pocket PC applications Via WiFi If TCP/IP via Bluetooth is available (I'm not technically Saavey to know if it is or not), then that would be a huge +, but not necessary. 2003 is a must, 2000 is almost as important, any other version would be nice. One catch: The protocol used to transmit to & from the server is coded into a C++ .Dll file. This .dll file can be constructed to your request, but the code that creates this .dll is native C++ which uses regular pointers. The .dll is not created in .Net, it's created in MSVC 6.0 Your application will need to utilize this native C++ .dll to generate the necessary packets to be passed to /from the server. Instructions on setting up the Windows 2000 &/or Windows 2003 PocketPC network settings. This should be constructed to utilize as many versions of Windows PocketPC software as possible.