I would like someone to convert approxiametely 50 Access forms to VB.NET ( Windows ). There are a number of 3rd Party OCX controls in use, specifically by dbi-tech and DevExpress. I would like these converted to a .NET equivalent. All of the OCX's that are in use are supported by classes built in VBA.
I would prefer someone who can build an architecture so that the forms that are built are inherited from base forms that share common functionality, like DAL, error handling, common toolbars, menus etc.
The ideal candidate will be be comfortable with both Microsoft Access 2003 and VB.NET 2003/2005.
Note: there are about 30 classes that will need to be converted as well from VBA to .NET.
There are reports to convert, however it is anticipated that a 3rd party tool would be used to convert these, probably Access2Crystal.
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).
* * *This broadcast message was sent to all bidders on Tuesday Jun 13, 2006 10:36:15 AM:
Yes, I would like to use the .NET equivalent controls from Dbi-tech and DevExpress. I would provide those if you don't have them.
Also, there are a number of well written classes that I would like converted as well, these can probably be converted by including them in a VB6 project and upsizing them to .NET that way.
The current back-end database is Access 2003. In a future project I would look at providing a SQL Server version as well.
There are actually many more forms to convert as part of a follow-up project, however the 50 most important will need to be converted first.
I will be sending out instructions on where to download screenshots and documentation as soon as I can.
miles at milestone dot ca
* * *This broadcast message was sent to all bidders on Friday Jun 30, 2006 8:50:37 AM:
I am still putting together a document with screenshots and information about the project. I have extended the bidding deadline accordingly to July 25, 2006.
Thanks for your patience.
Windows XP, .NET 1.1/2.0, VB.NET ( windows )