Request for Proposal (RFP): Migrate Access 2002 db to MS IE 3.0
Notices
Welcome to the "Web Projects" forums. Before you post, make sure you've selected the correct category based on the size of your project (in US dollars), or whether it is a partnership or "looking for work" request instead. Observe the guidelines for this section:
To all thread starters, check your "pm" box for responses, as that's how bidders will be communicating with you mainly using. You can turn on new pm notification by going to "User CP"-> "Edit Options"-> "Receive Email Notification of New Private Messages".
To respondents, avoid replying to a thread with a short generic response like "pm sent" as much as possible. It is pointless and clutters up the screen.
To respondents, don't reply to a work request with a summary of your resume. If you're not willing to spend the time to at least read the request and respond specifically to the request, then don't reply. The Web Projects forum isn't a place to get your resume/ portfolio posted on as many threads as possible, it's for the direct, human interaction between coder and client. Members who blanket the forums with their resume replies will be treated as spammers and banned.
To all thread starters, please update your thread's prefix to "resolved", when you've found a coder for your project or partnership (or wish to terminate the request). This is so coders don't waste time bidding on an invalid project. To do this, click on the "Edit" button under the first post of the thread, then the "Go Advanced" button. You have 14 days to update your thread's title.
Request for Proposal (RFP): Migrate Access 2002 db to MS IE 3.0
This is a Request for Proposals (RFP) to do the work described in this post for pay.
Description:
Think Javascript arrays... I need to migrate the database I created with Microsoft Access 2002 on Windows XP to Pocket Internet Explorer (same as IE 3.0) on NEC Mobilepro 780 HPC.
Target Platform:
Pocket Internet Explorer (same as IE 3.0) on Windows Ce handheld (HPC) device. Javascript, JScript, and HTML 3.2 compatible. No support for Java, VbScript, CSS, DHTML, or frames. Screen dimensions are 640 pixels wide by 214 pixels tall. The OS of the handheld device (HPC) is Windows Ce 2.11. The system architecture is MIPS 4121.
Source Prototype:
The Access 2002 database prototype is fully functional and ready to email to you as a zip file. It has 14 fully normalized (optimized) tables, only 4 of which have relationships between them. It has 2 forms, with text boxes as the only controls except for 2 combo boxes and (many) labels. Each of the 2 forms have multiple pages (tabs).
Specified Deliverables:
I want to migrate the database, including the forms, their controls, the tables, and the (in-process) HTML help system to Pocket Internet Explorer on the H/PC by utilizing Javascript arrays and web-based forms and controls.
Compensation:
Please make me an offer, but be fair and reasonable. I am an individual, not a company. I'm doing this project to help myself on a trip this summer.
Deadline:
Completion of beta deliverable by mid May '04. Completion of final deliverable by the end of May.
Offtopic: I'm having a little trouble conceptualizing how this would be done. With JS and HTML alone, the database itself would be read-only. More to the point, JS doesn't really lend itself well to relational tables design.
etalent: If you find someone to do this project for you, I'd appreciate finding out how they did it JS doesn't lend itself well to high-precision arithmetic either, but I did write a library to do that...
__________________
"The first step to confirming there is a bug in someone else's work is confirming there are no bugs in your own."
June 30, 2001
author, Verbosio prototype XML Editor
author, JavaScript Developer's Dictionary https://alexvincent.us/blog
Last edited by Alex Vincent; 04-30-2004 at 12:56 AM..
I don't understand what you are trying to do.
I don't understand why the complete backend should be changed just because the generated html will be displayed by another user agent. If this IE 3.0 can display html, then you can just use a db at the backend, and dynamically build the html-pages with a server side language like PHP or ASP or JSP or ...
This very same backend can then also be used to generate the same or similar html pages for another browser.
I researched EXTENSIVELY regarding relational database development with forms and SQL on the target platform (Win Ce 2.11 handheld). PHP, ASP, JPS are not supported on Pocket IE (same as IE 3.0).
The nearest thing I found that works for developing "native" databases in the target environment is Syware Visual Ce ($130), but the newest version does not support the target platform, so cab files would have to be downloaded from Syware to make Visual Ce backward compatible.
That whole idea stopped making sense when I realized that I already have a development environment in Pocket IE, albeit version 3.0. Still, if IE 3.0 can do Javascript, which it can, it suffices.
Pocket Access is the database included with Win Ce 2.11 on my handheld. If you're an Embedded Visual Basic programmer then that would be the obvious IDEAL solution. The biggest limitation I am aware of is that Pocket Access has a 67,000 record limit. Darn.
Please understand that I am not trying to complicate things. On the contrary, I've learned enough about what I'm trying to do to be dangerous. My prototype database works great on my desktop. Life would be wonderful if all I had to do was drag and drop it using ActiveSync, but no such luck.
Suggest away, please. Seeing my prototype Access 2002 database for yourself would clarify most everything, I bet. If you were just look to at it and then envision what it would take to emulate it on the target platform of Pocket IE or the equivalent IE 3.0.
Are you saying that you want to use webtechnology, but only the client side technology (in casu javascript and HTLM) ? And that you need a datasctructure of more then 67 000 records without using a database ? So that you would like to have a few pages that include a javascript array of more then 67 000 elements ?
I would rather not have a 67,000 record limitation.
Correct me if I'm wrong, please, but my understanding of arrays is that they are simply Javascript's way of doing databases.
If you can use Pocket Access as a backend rather than Javascript arrays, good. If you can get around the 67,000 record limtation, even better.
As numbers of pages goes, the prototype Access 2002 database has two forms. Each form has multiple pages (tabs). However, all the controls are text boxes with the exception of exactly two combo boxes and a bunch of labels.
Please keep asking me questions if I'm not being clear! -Thanks
Why am I getting this feeling that you are trying to do something simple in a very complicated way. Maybe if you started by describing your application and required functionality......
__________________ Vladdy | KL "Working web site is not the one that looks the same on common graphical browsers running on desktop computers, but the one that adequately delivers information regardless of device accessing it"
Correct me if I'm wrong, please, but my understanding of arrays is that they are simply Javascript's way of doing databases.
No not at all. An array in any language is simply a collection of related variables stored in memory. A database is a medium for storing data in files.
__________________
Spookster
CodingForums Supreme Overlord
All Hail Spookster
Who gave you that Ugging infraction? Yeah that's right it was me!
True, it is simple. I sure don't want to make it complicated. If you were to see the Access 2002 database for yourself, you'd see how simple it really is. Then you could formulate your own ideal solution instead of contending with my hack explanations.
As requested, here is a simplified description of what I need to pay someone to do for me. Before I get into it, I have to say that I have done this very thing, described my database, that is, on other discussion forums earlier in the development process. I found that doing so makes this simple database seem complicated. Seeing the database for yourself is much simpler, but I NEED THIS DONE! So, here I comply with your request...
Purpose:
Reference and data entry of the verbs and vocabulary of four languages (English, Spanish, Portuguese, and Kreyol).
Functionality:
Viewing or entering data with the use of one of two main forms at a time. Navigate each form with multiple pages (tabs). (1) Read the values populating the text boxes or (2) enter values into the textboxes.
Table Structure:
14 tables. 4 tables contain verbs data. The 4 verbs tables are related and fully normalized. The remaining 10 tables (fully normalized) contain vocabulary data and are not related.
Controls:
2 Forms, each with multiple pages (tabs). 14 text boxes. 2 combo boxes. Labels. A button on each form for toggling between each. A help button on each form to launch HTML help.
-----------------------
Please, please, please don't abandon this! Bear with me! I need this done! Propose away! Tell me something! Make me an offer! PLEASE!
What I do not understand is:
- Why do you need javascript and why do you care what the client is, when you can keep all the processing on the server and serve simple HTML forms (something IE3.0 can understand) to do the user interaction.
__________________ Vladdy | KL "Working web site is not the one that looks the same on common graphical browsers running on desktop computers, but the one that adequately delivers information regardless of device accessing it"
The database is to reside on a handheld computer, so it won't have any connectivity to a server or anything else. If you're thinking of making the handheld itself the server, great!
So you want it all to be a stand alone app on a hand-held... then why base it web technology in the first place??? Use VB, C++ or whatever to make an execuatable that runs in the target environment and works with your DB. You mentioned there is a limit to Access DB version - maybe the handheld can not handle your volume of data at all???
__________________ Vladdy | KL "Working web site is not the one that looks the same on common graphical browsers running on desktop computers, but the one that adequately delivers information regardless of device accessing it"
Yes, I want the database to be a stand along app on my handheld.
Based on my understanding of Pocket Internet Explorer, which is the equivalent of IE 3.2, and Javascript is that they (IE and Javascript) could serve as the development environment to which my original Access 2002 database could be migrated to.
By ALL MEANS, please propose your solution IN Embedded VB, C++, or, as you put it "whatever to make an executable that runs in the target environment and works" with my DB. I realize that I may have to accept the 76,000 record limitation.
If you can code in Javascript/IE 3.2, Embedded VB, C++, your mamas' army boots, whatever, please propose a solution to me! (weak attempt at humor there. I hope you don't mind.)
I'm not a programmer, so I defer to your recommendations! -Thanks!
I'm not the best person to do the handheld DB programming - just was trying to make sense of your requirements....
Good Luck in getting it done.
Just curious, is it something that you are developing for sale, or just a hobby project. In latter case, instead of paying someone to do the custom programming for you - use this money to buy yourself a new notebook (the latest Sony VAIOs are pretty light and compact) and use what you have now on it, without thinking about restrictions imposed by the handheld.
__________________ Vladdy | KL "Working web site is not the one that looks the same on common graphical browsers running on desktop computers, but the one that adequately delivers information regardless of device accessing it"