I am having a problem inserting a record using TADOQuery in Delphi 5. The query is open and active (the associated datasource state is in dsBrowse) when I try to perform the insert:
with DM.CustPartQuery do begin
Insert;
FieldByName('PKEY').AsStri
FieldByName('MCI_NBR').AsS
FieldByName('FILM_STATUS')
FieldByName('SUBCONTRACTED
end;
During debug I can see that after the insert statement, the datasource is still in dsBrowse mode. Then when it tries to assign the first field, I get an error "Dataset not in insert or edit mode"
What am I doing wrong?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
there can be a number of problems:
if your query is a join for example. or any other such "complex" sql.
or you have some master-detail or similar setup probably not configured correctly
or etc.
so .. what is your query looking like? (the sql) what otehr modifications have you made to the query and connection?
The query that I am using is pretty straightforward:
CustPartQuery.close;
with CustPartQuery.SQL do begin
Clear;
Text := 'SELECT * FROM CustomerParts WHERE MCINBR=''1%'''
end;
CustPartQuery.open;
I tried the various CursorLocation/CursorType per your response and all of the variations provided the same error (dataset not in edit or insert mode).
Hmm... try this:
with DM.CustPartQuery do begin
Insert;
FieldByName('PKEY').value:
FieldByName('MCI_NBR').val
FieldByName('FILM_STATUS')
FieldByName('SUBCONTRACTED
end;
I was always taught that those AsString and AsBoolean are readonly values.
I did check to make sure the query was not empty prior to the insert. As far as not using AsString, etc., the problem is during the Insert statement. When I debug, the dataset is still in Browse mode immediately after the Insert statement before it does the replacement statements.
I ended up using an INSERT INTO query instead to add the record and that seems to work fine.
This question can be closed.
Business Accounts
Answer for Membership
by: developmentguruPosted on 2007-11-21 at 05:52:15ID: 20327593
It may help to see the query that is active at the time you are trying to do the insert. Certain queries can produce result sets that are not easily updatable. Are all of the fields in the same table?
You should check the values of the CursorLocation and CursorType properties (both at design time and ruin time). If the cursor location is clUseClient then the only valid CursorType is stStatic. I would set the cursor location to ctServer and the CursorType to ctKeySet or ctDynamic and see if it works.
Personally I use the ADOQuery to populate a TClientDataset and browse off of that. This will allow you to edit everything in memory and discard changes if you wish. This works best with a relatively small set of records although I have done it with roughly 20,000). Once the user decides to accept their changes you can cycle through the dataset looking for records whos fields that have been modified or added. In general added records will have no auto populated ID (one way to test for an inserted record). Generally I use insert and update query statements to update the database (using transactions if appropriate), then repopulate my ClientDataset from the database.
Let me know if you need more.