Hi
I think I've narrowed it down - although the exception (seems) to have been raised at the point of clicking the button that runs the opendialog.execute command for the second time, it appears that this isn't the case. I've moved the code that dealt with creation of a DBISAM in memory table...
As suggested, here's the minimum code that doesn't include any attempts by me to fix the issue:
procedure TForm1.Button1Click(Sender: TObject);
begin
With DBISAMTable1 do
Begin
DatabaseName:='Memory';
TableName:='NewTable';
if not exists then
begin
with FieldDefs do
begin...
Yup - again this was to see whether it was because I wasn't freeing them up that was causing the problem, these calls to .free() were added to try to solve the problem but haven't.
Cheers
Martin
Hi
To be honest I've only added that line to check whether it solved the problem (which needless to say it didn't) - the app bombs out with or without it. Is there anything obvious I'm doing?
Thanks again
Martin
Hi
I've searched the forums here for problems using the OpenDialog control but nothing similar seems to have been posted before.
I've been asked to put together a file import app to get some info imported into a DBISAM DB which I'm progressing with, albeit slowly as I'm new to both Delphi and...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.