Show Bid Request
VB code to remove referential integrity and change primary key in Access 2K db
Bid Request Id: 46469
|
|
|
|
Posted by: |
infomed (37 ratings)
(Software buyer rating 10 )
|
|
Non-action Ratio: |
Very Good - 14.81%
|
Buyer Security Verifications: |
Good
|
|
Approved on: |
Feb 2, 2003
5:53:34 PM EDT
|
|
Bidding Closes: |
Feb 16, 2003
5:52:25 PM EDT
|
|
Viewed (by coders): |
211 times
|
|
|
|
|
Description:
I have a database (see attached) that has some primary keys and referential integrity setup. This, though, has led to some problems when data gets corrupted.
I therefore want to change the way these databases are setup, though they currently have data in them that can't be damaged.
I want to do the following (unless you have a better recommendation), but it MUST be through VB code that I will add to my project:
1. If the links still exist (I've removed them manually from some databases), remove the links between tables in the Access Relationships.
2. If the primary key still exists, remove the primary care field in the Demographics and SOAP tables, though leave the field as the same name and same data with the autonumber, incremental and indexed without duplicates allowed.
3. Add a new primary key to each table (shouldn't I do this?) called primekey and autonumber it.
Does this bid make sense? Any suggestions or comments?
The database is password protected: "123" and must remain so.
Since I've been burned on RAC before by folks who swear they can do it, then can't really get the job done, I only consider bids with the code (or a demo) up front.
Don't spend much time on the GUI as I'm just going to use the procedures in my own project when I update the databases.
Thanks! Looking forward to seeing what you can do...
Deliverables:
1) Complete and fully-functional working source code of all work done.
3) Complete ownership and distribution copyrights to all work purchased.
Platform:
win 32 bit
Additional Files:
This bid request includes IMPORTANT additional attached files. Please download and read fully before bidding.
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 |
|
|
|
|
N/A
|
Feb 2, 2003
6:32:41 PM EDT
|
9.55
(Excellent)
|
|
|
So all you want is for the VB program to access the database and remove the referential integrity links, and set primary keys, etc. So there would just need to be a way to put in the path of the database. This could be commandline and/or form with file browser. I thing that this would be easier with DAO than ADO, as DAO is specific to Access DB. Please let me know your preferences is they are different. I will have a demo in 24 hours, and let you know about price then.
|
|
|
|
|
This bid was accepted by the buyer!
|
$35 (USD)
|
Feb 3, 2003
7:02:14 PM EDT
|
9.55
(Excellent)
|
|
|
Hi,
I have done parts 1 and
2. They were pretty straight forward, but there is
problem with 3.
You wanted a COUNTER
field to be added to each table. However for tables that already have an
AUTOINCREMENT field, you cannot add one
as only one is allowed per table. Also as part of your request you said
'(shouldn't I do this?)'. To that I would say no you should not. You have
requested the code to remove automatic referential integrity and that is a
good idea, especially if you are controlling your database with a VB app.
In fact my suggestion is that you should remove all constraints for a
database that is used in a custom application. Your application will take
care of the logic of the parent child relationships and primary keys,
etc.When you have constraints, it makes programming difficult, beause you
have to make sure that you do everything in the correct sequence to
satisfy those rules. Often this sequence may not be the most appropriate
or logical way to achieve your objective. When I write custom database
apps I usually do not create relationships or any other constraints (even
indices). Then I just let the logic of my code do all that stuff.
Anyway I have attached my code so far so that does 1
and 2. I have left
the code in that I use to add the [primekey] field to each table so you
can see how I would do it, but I have commented it out. The program as it
is just automatically executes the changes on the AC.MDB file in
its current folder and ends. To test it you should put it in a folder and
copy your database there. Then open the database check out the relationships
and indices, and then run the program and then re-check the db. We can
discuss how you wan it finished off if you accept my bid,
Thanks
Peter
Lovell
|
|
|
Attached File
|
|
|
|
|
|
N/A
|
Feb 3, 2003
7:06:04 PM EDT
|
9.55
(Excellent)
|
|
|
UPDATE: sorry I think I did not save my last changes in the previous attachment,
Peter Lovell
|
|
|
Attached File
|
|
|
|
|
|