Subject | RE: [IBO] Losing TIB_Connection whilst designing |
---|---|
Author | Helen Borrie |
Post date | 2003-02-19T11:57:47Z |
At 11:46 AM 19/02/2003 +0000, you wrote:
within the last few weeks, advising against using DatabaseName, and I'm in
the process of a review and update of the GSG at the moment, where I will
set that one straight.
Yes, still replace the auto-duplicated path with an alias and, if you need
to set or change the database path at run-time, set the Path and Server
properties, don't do it via DatabaseName.
regards,
Helen
>Hi Helen,I don't think anything has been updated; but Jason responded to a question
>
>I'm a bit puzzled by your statement that we "*Don't* use the DatabaseName
>property" because the GSG advises that we should use it.
>
>Extract from 'Populating the data module' :
>
>For the connection :
>
>'If you don't enter anything for the DatabaseName property, it will default
>to the Database property value. Because that could be quite lengthy - and
>will probably change when you deploy your app - you are strongly advised to
>make use of this alias feature for use in your client-side code.'
>
>For the queries :
>
>'Notice that the IB_Query's DatabaseName property has been set to the alias
>that was entered into the Databasename property of the IB_Connection. As we
>shall see, making this the FIRST thing we do after naming the IB_Query is
>going to save a LOT of typing...'
>
>
>Has something been updated to change what the GSG is advising ?
within the last few weeks, advising against using DatabaseName, and I'm in
the process of a review and update of the GSG at the moment, where I will
set that one straight.
Yes, still replace the auto-duplicated path with an alias and, if you need
to set or change the database path at run-time, set the Path and Server
properties, don't do it via DatabaseName.
regards,
Helen