Hello.

I experienced a strange issue with Dbisam today resulting in the
AV/exception message "SessionName MySession_1 is not a valid session". I
will try to explain:

I have a datamodule with a Session (MySession), where the property
AutoSessionName is True.
When I try to run the application I get an AV/Exception saying "SessionName
MySession_1 is not a valid session", so I go to debug, and quicly realise
that this exception was generated before my code was invoked. So it looked
like a Dbisam error.
So I change the AutoSessionName to false, and the problem is apparently
resolved. If I switch back to AutoSessionName = True the exception occurs
again.

Ok, so I boot the computer, and hope that this invalid session is gone, but
NOT. The same situation occurs.

Now I set the AutoSessionName = False, run the application, and save the
project, close Delphi, and Turn the computer off and start it again.

This time when I open my project, the SessionName has been set to
"MySession_2", and AutoSessionName = True works again....

What happened?
And how do you manage these sessions, files on the harddrive, in memory, or?

Regards
Petter Topp
Windows VISTA
D 2007
Dbisam 4.25

Sorry for the From Name, a mistake in creation of the account...


"news.elevatesoft.com" <petter.topp@atcdata.no> skrev i melding
news:C533E4FD-1304-4E61-8012-D74468667B2A@news.elevatesoft.com...
> Hello.
>
> I experienced a strange issue with Dbisam today resulting in the
> AV/exception message "SessionName MySession_1 is not a valid session". I
> will try to explain:
>
> I have a datamodule with a Session (MySession), where the property
> AutoSessionName is True.
> When I try to run the application I get an AV/Exception saying
> "SessionName MySession_1 is not a valid session", so I go to debug, and
> quicly realise that this exception was generated before my code was
> invoked. So it looked like a Dbisam error.
> So I change the AutoSessionName to false, and the problem is apparently
> resolved. If I switch back to AutoSessionName = True the exception occurs
> again.
>
> Ok, so I boot the computer, and hope that this invalid session is gone,
> but NOT. The same situation occurs.
>
> Now I set the AutoSessionName = False, run the application, and save the
> project, close Delphi, and Turn the computer off and start it again.
>
> This time when I open my project, the SessionName has been set to
> "MySession_2", and AutoSessionName = True works again....
>
> What happened?
> And how do you manage these sessions, files on the harddrive, in memory,
> or?
>
> Regards
> Petter Topp
> Windows VISTA
> D 2007
> Dbisam 4.25
>

Petter,

<< I have a datamodule with a Session (MySession), where the property
AutoSessionName is True. When I try to run the application I get an
AV/Exception saying "SessionName MySession_1 is not a valid session", so I
go to debug, and quicly realise that this exception was generated before my
code was invoked. So it looked like a Dbisam error. >>

This almost always caused by having a form with a DBISAM component on it
that references the SessionName in question, but is auto-created *before*
the data module.  The solution is to make sure that the data module is the
first listed module in the project form/module creation order.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim.

I do have one form that have a Dbisam table on it, and is auto created
before the datamodule in question.
However, this Dbisam table have no references to any session, database, or
table at designtime, and there is no create event that assigns these
objects.

The thing is that the situation was resolved without any changes to the
code, just change of the AutoSessionName and a couple of reboots...

This is no big issue. This is the first time I have experienced this, and I
thought that it might be fine to understand what's going on...

Regards
Petter Topp

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> skrev i melding
news:FEADE877-D4BD-487C-9CB2-F83C35FE3865@news.elevatesoft.com...
> Petter,
>
> << I have a datamodule with a Session (MySession), where the property
> AutoSessionName is True. When I try to run the application I get an
> AV/Exception saying "SessionName MySession_1 is not a valid session", so I
> go to debug, and quicly realise that this exception was generated before
> my code was invoked. So it looked like a Dbisam error. >>
>
> This almost always caused by having a form with a DBISAM component on it
> that references the SessionName in question, but is auto-created *before*
> the data module.  The solution is to make sure that the data module is the
> first listed module in the project form/module creation order.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Petter,

<< I do have one form that have a Dbisam table on it, and is auto created
before the datamodule in question. However, this Dbisam table have no
references to any session, database, or table at designtime, and there is no
create event that assigns these objects. >>

Did you check the creation order of the DBISAM components on the data module
itself ?  The session should be created first, before the other DBISAM
components.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:E637DA80-A146-4E89-9064-7D4633F5163E@news.elevatesoft.com...
> Petter,
>
> << I do have one form that have a Dbisam table on it, and is auto created
> before the datamodule in question. However, this Dbisam table have no
> references to any session, database, or table at designtime, and there is
> no create event that assigns these objects. >>
>
> Did you check the creation order of the DBISAM components on the data
> module itself ?  The session should be created first, before the other
> DBISAM components.
>

The key IMO is to make sure that the DBISAM components are not active when
you compile the program.

Robert