Roy,

<< I personally find it easier mainly I think because it allows me to put in
user id & password - saves me having to type it in when setting everything
up in the IDE (naturally these are the development ones and strangely enough
user XX doesn't seem to exist on any of the live systems . >>

Which user ID and password are you referring to ?  The session user ID and
password are separate from the Local* engine properties.

Tim Young
Elevate Software
www.elevatesoft.com

Tim

><< I personally find it easier mainly I think because it allows me to put in
>user id & password - saves me having to type it in when setting everything
>up in the IDE (naturally these are the development ones and strangely enough
>user XX doesn't seem to exist on any of the live systems . >>
>
>Which user ID and password are you referring to ? The session user ID and
>password are separate from the Local* engine properties.

I think I see where you're coming from. I'm referring to LoginUser & LoginPassword which I agree aren't prefixed with Local which I assume means that they aren't part of the Local* engine properties.

Trying to reconstruct my thought process from way back (has ElevateDB really been out THAT long) I suppose they went:

1. I need a session on the form because I want to connect to the database and open tables at design time and I dislike having to keep typing a userID / password

2. I've got this session and it has this section called local - well I'm not using remote access so that sounds right

3. That means I have to set UseLocalSessionEngineSettings to True

There is a side benefit. One I've set UseLocalSessionEngineSettings to True I can essentially ignore the engine component.

Roy Lambert

Hi Tim,

> If you want things to be as close to DBISAM as possible, then do this:
<Snip>

That's fantastic stuff Tim - I'll be putting that away in my little
Knowledgebase.

Cheers

Adam.