Show Bid Request
Database system
Bid Request Id: 37580
|
|
|
Posted by: |
RockinRon (2 ratings)
(Software buyer rating 10)
|
Non-action Ratio: |
Very Good - 0.00%
|
Buyer Security Verifications: |
Good
|
Approved on: |
Nov 29, 2002 2:46:17 PM EDT
|
Bidding Closes: |
Dec 13, 2002 2:59:51 PM EDT
|
Viewed (by coders): |
464 times
|
Deadline: |
1/6/2003
TIME EXPIRED
|
|
|
|
Description:
Database System, multi user, network ready.
Deliverables: need speed, especially on a network.(server, peer to peer, etc.)
Store These fields: Important Note: do NOT use a grid for data entry, use text boxes
1. Name( in One Field) 2. Date(in one field)(month & day only)Example: 10-02 is 10th month, second day. always 5 charactors.
3. Age (as integer)( Use combo box to enter age from 1 to 100) 4. Notes as string of charactors up to 3000 (using textbox) 5. User name(one field)
VERY IMPORTANT! i want to "Lock Out" the data from viewing or ANY use by ANY other database viewer(access, excel, etc.) give details on this feature if needed. this is very important.
Show how how to create, empty a record and re-use it later when a new record is required.
i also need to assign a number(numbers & letters combined) to each created record that would NEVER be deleted so they can be tracked by this record number. i need to track the total amount of records at all times.
opening screen is for data entry\edit. (command buttons will take you to any other required features) i would want to scroll thru current records on the opening screen by using a vertical scroll bar and view\edit any or all fields at any time.
display all data from all records in flexgrid W\command button
Important Note: sort by date\day when loading flexgrid. example: the dates 10-12 would be listed after 10-11 and so on
document ALL details of code purpose including what kind of forms to use Note: I would like to use standard Exe's if possible.
also, tool(s) needed to load my existing "flat" file data into the new database. "Flat" file> i use the "Open", "Get", & "Put" statements Note: Flat files are too slow when i go above 5000 reports. 2500 records take about 5-6 seconds to load all into a flexgrid on a 1.6 ghz pent4, this is way too slow. even slower on a network system.(60-90 seconds)
Note: I am very experienced with "Flat" files but have NO experience in the new database systems. I do not know if the the new systems have record numbers or if i have to add them so i need info pertaining to record id methods.
anything that can increase speed when searching records or loading a flexgrid would be a plus.
show how to add fields at a later time.
needs to be able to handle up to 32,000 records and access\read them very fast when loading into a flexgrid.
I need to know how to name the file for the database so i can attach the file year to the file name.
Example: Icd02.dat is for the current year. Each year will start a new database, the previous year will have to be available for view\edit as required. each previous year database will be accessable with a combo box to select the previous year(s). i know how to do year selection with "Flat" files but i may need info to do it with this new system.
show how to search any field in all records for a certain word, phrase or number and do it fast
built-in edit Prevention system: each record will have a user name, i want to be able to prevent any user from editing the record UNLESS the current username matches the current record username.
Note: i will have a variable: TerminalUserName that will contain the current user name, if it matches the current record "user name" then editing will be allowed of the current record.
very basic printing of a single record
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request.
3) Complete ownership and distribution copyrights to all work purchased.
Platform:
Win98, Win2000, Xp Home & XP Pro, Xp Office, WinME.
Must be 100% finished and received by buyer on:
Jan 6, 2003 EDT
Deadline legal notes: All times are expressed in the time zone of the site EDT (UT - 5). If the buyer omitted a time, then the deadline is 11:59:59 PM EDT on the indicated date.
Special Conditions / Other:
if the project is completed and approved BEFORE 12/24/02 then a $20 bonus will be given.
Remember that contacting the other party outside of the site (by email, phone, etc.) on all business projects < $500 (before the buyer's money is escrowed) is a violation of both the software buyer and seller agreements.
We monitor all site activity for such violations and can instantly expel transgressers on the spot, so we thank you in advance for your cooperation.
If you notice a violation please help out the site and report it. Thanks for your help.
|
|
Bidding/Comments:
|
All monetary amounts on the site are in United States dollars.
Rent a Coder is a closed auction, so coders can only see their own bids and comments. Buyers can view every posting made on their bid requests. |
See all rejected bids (and all comments)
Name |
Bid Amount |
Date |
Coder Rating |
|
|
|
This bid was accepted by the buyer!
|
$200 (USD)
|
Nov 29, 2002 5:43:30 PM EDT
|
10
(Excellent)
|
|
|
I could do this easily by the December 24th optimistic date. The platform would be Visual Basic 6.0, Access 97 (would also work with Access 2000).
Unfortunately, to distribute a database application you also need to distribute the Microsoft Data Access Components which is 7.5 mb of data! (unless you know that all of your users will already have the mdac installed - I believe that with XP this is the case).
A Visual Basic application requires more than just the EXE, it also requires several additional DLLs, an OCX or two, and the MDAC I described above.
A couple of points on your requirement. It's very hard to totally secure a database that is anything less than a full implementation of SQL Server or Oracle.
In Access the things that can be done are these:
Secure the database with a Password so that it can be opened only with the correct password.
Encrypt the contents so that even if the password were provided, the contents would not be readable.
Still, someone could conceivably delete the .mdb file or if they were able to break the password, they could change the contents or delete records even if they couldn't read the contents of the fields.
Message me back if you have more to discuss about this aspect of your requirement before you accept my bid.
I'd suggest that you only have one database, even for all years. Year can be an additional column in your database and you can limit the data selected by year for viewing. This allows the user to switch to different years and review the data without managing multiple database files. Speed should not be an issue. If it is, alternate designs are possible with archival tables.
Your comment about blanking out records and re-using them is not clear. Normally, in a database environment, you will either Update a record by typing over it, Insert a new record, or Delete an existing record.
As far as loading from a flat file, it sounds like that is an administrative function that only needs to occur occassionally? Once the data is loaded into the db, the normal user will be reading and updating the database, not the flat file, correct?
|
|
|
|
|
|