Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread Likely Dumb Questions
Tue, Jan 21 2014 12:11 AMPermanent Link

Sean McDermott

I have a db that I want to connect to locally (peer to peer) and also using dbsrvr (client server). For the remote access I use a session component and all works well as long as the database tables and queries are set to the session name. When I try a local connect the db isn't found because of the session name property of the tables and queries is expecting a remote connection via the session component. So...

For remote access I need the session component but for the local access I currently just disable it.

1) Does this make sense or for local access should I always stick with the session and set the sessiontype to stlocal?
2) Do I need to re-assign the sessionname for each table and component back to 'default' to connect locally versus remotely? This works when I do it but it isn't pretty.

Thanks, Sean
Tue, Jan 21 2014 9:50 AMPermanent Link

Fernando Dias

Team Elevate Team Elevate

Sean,

You can use the same TDBISAMSession component in both cases and you don't have to disable anything or change the SessionName.

Just set the TDBISAMSession.SessionType to stLocal and the TDBISAMDatabase.Directory to the local directory where the tables are for local access

OR

TDBISAMSession.SessionType to stRemote and the TDBISAM.RemoteDatabase to the name of the remote database for remote access.

--
Fernando Dias
[Team Elevate]
Tue, Jan 21 2014 9:53 AMPermanent Link

Fernando Dias

Team Elevate Team Elevate

Correction:

It should be "TDBISAMDatabase.RemoteDatabase" instead of "TDBISAM.RemoteDatabase"

--
Fernando Dias
[Team Elevate]
Thu, Jan 23 2014 11:37 PMPermanent Link

Sean McDermott

Thanks Fernando, works great, Sean

Fernando Dias wrote:

Correction:

It should be "TDBISAMDatabase.RemoteDatabase" instead of "TDBISAM.RemoteDatabase"

--
Fernando Dias
[Team Elevate]
Image