Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 3 of 3 total
Thread Session name is not valid.
Thu, Sep 18 2008 7:32 AMPermanent Link

Frank
I have a couple of projects that contain a TDBISAMSession object.  The object name is sesMaterials and SessionName is 'Materials'.  
When I open the project I see several dialogs with the following message:  "Session name Materials is not valid."  I can hit "OK" through
each and then everything seems to be fine.  Is there a way to avoid the nuisance of the dialogs?
Thu, Sep 18 2008 8:38 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Frank


>I have a couple of projects that contain a TDBISAMSession object. The object name is sesMaterials and SessionName is 'Materials'.
>When I open the project I see several dialogs with the following message: "Session name Materials is not valid." I can hit "OK" through
>each and then everything seems to be fine. Is there a way to avoid the nuisance of the dialogs?

The best way is to find out what the problem is Smiley From what you've posted I don't think the error is coming from the session itself since there should only be one instance of a session with that name. Its more likely to be one or more of the components linked to the session or possibly you're trying to instantiate the session several times?

Roy Lambert [Team Elevate]
Thu, Sep 18 2008 10:54 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Frank,

<< I have a couple of projects that contain a TDBISAMSession object.  The
object name is sesMaterials and SessionName is 'Materials'.  When I open the
project I see several dialogs with the following message:  "Session name
Materials is not valid."  I can hit "OK" through each and then everything
seems to be fine.  Is there a way to avoid the nuisance of the dialogs? >>

Does your project contain open forms that contain DBISAM components whose
SessionName is set to 'Materials' ?  If so, then you need to make sure of
two things:

1) That the form or data module that contains the sesMaterials
TDBISAMSession component is also available on an open form or data module.

2) That the creation order of the DBISAM components on any form or data
module is set properly so that the session is created before any other
DBISAM components that may link to it via their SessionName property.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image