Hi,

I'm having this issue with DBISAM 4.41b1 in Delphi XE2.

It seems every time I go to close down my application in the IDE I get
this error message.

"Access Violation at address xxxxx in module rtl160.bpl"

If I reopen the Delphi and my application again, I get errors such as:

Session Name 'DBS' already exists and Database Name 'DB' already exists.

The TDBISAMSession and TDBISAMDatabase components which were once active
are deactivated on my main form once they show. (They're normally
activated).

Keeping these components deactivated stops the RTL160.bpl errors from
occurring.

This occurs in Delphi XE2, but not in Delphi 2007.

I've tried uninstalling and reinstalling DBISam - which seems to work OK
for the first few times, and then the error comes back again.

It doesn't appear to affect the underlying application when compiled,
just within the IDE.

Searching the interweb sources seem to indicate that RTL160.bpl errors
are due to a bug within the Design Time package, but as mentioned I have
no issues with Delphi 2007.

Just wondering if anyone else has come across this, and has any advise?

Cheers

Adam.

On 6/3/2015 7:42 PM, Adam H. wrote:
> I'm having this issue with DBISAM 4.41b1 in Delphi XE2.
> It seems every time I go to close down my application in the IDE I get
> this error message.
> "Access Violation at address xxxxx in module rtl160.bpl"
> Just wondering if anyone else has come across this, and has any advise?

I'm running XE2 with 4.41b1 as well and not seeing this here.

I do not normally have a session/db active but tried with a test app
that has a session, database and table with all of them active. app runs
ok and i can close and reopen ide with no errors (and they all remain
active). Tried half a dozen times to run and recompile and
close/relaunch delphi.

Any chance you have some custom components or other packages (with
dbisam) in the IDE (even the elevate ones to recompile dbsys etc) ?

If you have additional steps you'd like me try to reproduce this let me
know.

Raul

Hi Raul,

Thanks for your response and confirmation that you don't have the same
issue on XE2...

I can't find any custom components that are installed that reference DBISam.

I do have DBSYS but it wasn't running when this error occurred.

However I neglected to mention that this error has only occurred after
updating to the latest patch / build of XE2. (XE2 Update 4 Hotfix 1)

I was fine on XE2 until then.

Never had the problem prior to this. Just wondering if you can please
confirm what version of XE2 you are running, and if it's Update 4 Hotfix 1?

Cheers

Adam.

On 6/3/2015 9:17 PM, Adam H. wrote:
> Never had the problem prior to this. Just wondering if you can please
> confirm what version of XE2 you are running, and if it's Update 4 Hotfix 1?

Adam,

I'm running XE2 version 16.0.4504.48759

Under installed updates i have:
Delphi XE2 amd C++ Builder XE Update 4 HotFix 1
Help Update 6 For Delphi XE2 and C++ Builder XE2

I have not updated this installation for a while so it's been on this
version for few years i'd guess.

It's also in a VM so there is really nothing other than Windows, XE2 and
components (i don't have any other delphis installed alongside as my
rule is one VM per delphi).


Raul

Hi Raul,

Thanks for the clarification. Not sure what's going on.

Like you, I have mine in a VM dedicated just for that installation of
Delphi. No other versions running parallel.

I guess this might be a good excuse for a clean rebuild when Windows 10
comes out, to see whether or not that fixes the issue. In the mean time
I'll just persist with it.

Thanks again...

Adam.

Adam H. wrote:

> The TDBISAMSession and TDBISAMDatabase components which were once
> active are deactivated on my main form once they show. (They're
> normally activated).

This strikes me as something I would want clarity on. In the Delphi
project, in the IDE, these should be inactive. Don't choose to
de-activate them in the application startup, like FormCreate. You want
them positively inactive until you want them active. Me, I have a
little application that parses the forms and removes the active
property from database components, and that is run in my FinalBuilder
script.

The other thing I'd like to know is if you have any "single instance
executable" code? Something that means that if your code is already
running, it switches to that one instead of starting a new instance. If
you do, then I wonder if the application is not closing properly, and
then the next time you run it it is kicking the crashed one and it
fails.

Apart from that, I've been using DBISAM in XE2 for years, and not had
any problems.

--

Matthew Jones

Hi Matthew,

Thanks for your reply...

In the Delphi project I'm happy for them to be deactive by default,
however they automatically activate everytime in designtime that I
perform an action on a connected component. (Adding TPersistent fields
to a TDBISAMTable or TDBISAMQuery, run a report, connect to a grid, etc)...

Unless I remember each time to deactivate them before I save a project
they close in active.

This has never been a problem before. There are no datasets on the
mainform / autocreate form that are active by default, so there's no
issues there - the only issue is within the IDE itself when the project
is closed or reopened with this access violation message.

Your final build script idea is interesting, but I don't see how this
would work in this instance, as it would only deactivate them when the
project is built, not every time I close and open it to develop on.

I do have a single instance executable code within the application as
well. (Although this can be overridden with a parameter at startup).

However keep in mind that the error I am having is specifically to the
IDE. I have no problems at all with the compiled application, either
running single, or multi instances, and regardless of how many times I
close or open it.

The problem is isolated just to the IDE and when the project is opened
or closed in the IDE. (ie, no runtime).

Best Regards

Adam.

Adam


If GExperts runs in XE2 it has an option to set the value of properties. I use it to deactivate all the Elevate stuff

Roy Lambert

Adam H. wrote:

> The problem is isolated just to the IDE and when the project is
> opened or closed in the IDE. (ie, no runtime).

Hmm, I think I'd double check that the session components are indeed
not duplicated. There must be something that the IDE is doing, or not
doing, that is causing this. Do you have datamodules referenced from
forms, or inheritance at all? Datamodules and inheritance cause me
trouble in some of my projects as the IDE tells me that it cannot close
something because it is linked by a form that is open, even though it
isn't really open but is because of the inheritance and a form that is
open. I find I have to close everything, then the IDE, and then I can
edit the thing I'm wanting. (Details fuzzy because it is a while since
I worked on that.)

Anyway, the simple answer is that DBISAM doesn't have a problem in
general, so there is something about your setup that is causing this.
If you can pin it down, then we can perhaps suggest ways around it, but
keeping it inactive would help (as Roy says, there are add-ins that can
de-activate database components on save).

--

Matthew Jones

Hi Roy,

> If GExperts runs in XE2 it has an option to set the value of properties. I use it to deactivate all the Elevate stuff

Cheers - I'll give that a shot. It should work as a good workaround for
me. Thank you.

Adam