Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Incident Reports » Incident Reports Reported for Version 3.10 » View Incident Report |
Serious |
Reported By: Andreas Jaeke Reported On: 5/23/2002 For: Version 3.10 Build 1 |
Put a DBISAMSession, a DBISAMDatabase and a DBISAMQuery on a formular and configure it properly to be connected to a remote DBISAM-server. Set DBISAMQuery.RequestLive to TRUE. Then the code : DBISAMQuery1.SQL.Clear; DBISAMQuery1.SQL.Add ( 'SELECT' + #13#10 + ' *' + #13#10 + 'FROM' + #13#10 + ' exampletable'; ); DBISAMQuery1.ExecSQL; DBISAMQuery1.Open; DBISAMQuery1.First; DBISAMQuery1.Edit; DBISAMQuery1.FieldByName('examplememo').AsString := ''; try DBISAMQuery1.Delete; except on E: Exception do begin Memo1.Lines.Add('Exception deleting record after setting ' + 'memo (as string) to '''': ' + #13#10 + E.Message); Exit; end; end; should write the exeption to the memo (I forgot to mention before ;-) If you do a DBISAMQuery1.Post before the try-except-block all will go well. In the end it's an easy to avoid behaviour, but it's a little irritating I think.
This web page was last updated on Wednesday, October 30, 2024 at 11:41 AM | Privacy PolicySite Map © 2025 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |