September 3, 2003 at 6:53 am
Hello,
I am developing using ADO to access my server. I have two tables, Appts and EmpAppts. Appts holds basic information about the appointment whilst EmpAppt allows me to have more than one employee involved in the same appointment. Currently i use a stored procedure to reutrn my result set. Now with this result set i feed a data aware planner. Whenever i try to delete an appointment from the planner i get the error message, "Insufficient key column information for updating or refreshing." I am aware that this is a bug in the ADO technology that essentially boils down to ADO not being able to narrow down the delete to one record in both joined tables. I have seen the KB articles but i am still unable to resolve a work around. Both tables have a primary key and i have tried implementing a foreign key with cascading deletes but none the less i am having no success. Does anyone have any ideas on how to get around this?
Thank you,
brian
PS Enviroment: Delphi 7 Ent, SQL Server 2000 Dev, MDAC 2.8
Think great, be great!
September 3, 2003 at 9:05 am
Hi Brian,
can you post what you've got so far? SQL Statement, Delphi code...
Cheers,
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
September 3, 2003 at 9:43 am
Mr. Kalis,
Thank you for time. However, i have found a workaround. Its rather ugly but it works. I essentially had to close the active dataset and manually do the delete with an ADOCommand for both tables. I do appreciate your acknowlegement.
sincerely,
brian
Think great, be great!
September 3, 2003 at 1:16 pm
Seems like there is an extended property that lets you give it enough info to do the delete.
Andy
September 3, 2003 at 1:30 pm
If your making reference to the Unique Table extended property, i am not sure how to implement this? I am currently using a stored procedure to get my result set. Can the extended properties be applied in the same way as a table or query as you mention?
Think great, be great!
September 3, 2003 at 2:05 pm
See if this helps:
Andy
September 4, 2003 at 12:24 am
Glad to hear you solved your problem!
quote:
Mr. Kalis,
hm, I feel not very confident when someone speaks that formally to me
So, if you don't have any problems with this, just call me Frank. Ok?
Cheers,
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
September 4, 2003 at 7:35 am
Frank,
I apologize. I was just being polite. I do appreciate your time.
thanks,
brian
Think great, be great!
September 4, 2003 at 7:40 am
quote:
I apologize. I was just being polite. I do appreciate your time.
there is nothing wrong with being polite, but in such cases it reminds me of:
- my wife, before putting my head in the right place again
- my boss, doing the same
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy