Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Locate

3 posts in Delphi Last posting was on 2003-08-30 15:50:25.0Z
Teunis Middelkoop Posted on 2003-08-29 01:02:49.0Z
Message-ID: <3F4EA639.26A60B42@attglobal.net>
Date: Thu, 28 Aug 2003 21:02:49 -0400
From: Teunis Middelkoop <teunislc@attglobal.net>
Reply-To: teunislc@attglobal.net
Organization: Logical Connections Ltd.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD NSCPCD47 (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: advantage.delphi
Subject: Locate
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 32.105.11.21
X-Trace: 28 Aug 2003 18:33:34 -0700, 32.105.11.21
Lines: 11
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!32.105.11.21
Xref: solutions.advantagedatabase.com Advantage.Delphi:13805
Article PK: 1107240

A table (ADT and ADI) was copied from a CD to a database, controled by
ALS 6.11 The read only property was changed to archive.
In a program there is a call to the Locate function of the Table the
result is FALSE.
The table was reindexed and after that the locate works fine.
It worries me that the locate function does not give a warning like
index out of date, index corrupted or whatever.
I prefer rt errors above false results.
By the way, I am very content with the TAdsDelphiComponents.
Should I reindex tables when moving them from one to another database??
Teunis


Joachim Duerr (ADS Support) Posted on 2003-08-29 07:56:46.0Z
From: "Joachim Duerr (ADS Support)" <jojo.duerr@gmx.de>
Subject: Re: Locate
Newsgroups: Advantage.Delphi
References: <3F4EA639.26A60B42@attglobal.net>
Organization: Extended Systems GmbH
User-Agent: XanaNews/1.15.6.2
X-Face: ,QMv7[luB)BpWAQ~:"kw6n%0ieY63.:g2K3n~8ky0;||5Xle*Xq+=~<Fy:0CVC2nx@8~vZ
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
NNTP-Posting-Host: 195.2.185.25
Message-ID: <3f4ef92e@solutions.advantagedatabase.com>
Date: 29 Aug 2003 00:56:46 -0700
X-Trace: 29 Aug 2003 00:56:46 -0700, 195.2.185.25
Lines: 34
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!195.2.185.25
Xref: solutions.advantagedatabase.com Advantage.Delphi:13806
Article PK: 1107243


Teunis Middelkoop wrote in <3F4EA639.26A60B42@attglobal.net> :

> A table (ADT and ADI) was copied from a CD to a database, controled by
> ALS 6.11 The read only property was changed to archive.
> In a program there is a call to the Locate function of the Table the
> result is FALSE.
> The table was reindexed and after that the locate works fine.
> It worries me that the locate function does not give a warning like
> index out of date, index corrupted or whatever.
> I prefer rt errors above false results.

If the ADT and the ADI came from the same location and it worked there
before, I guess that you have different collation sequences set on the
machines. If ADS would check logical index corruptions on opening the
table, this would result in a huge performance loss and the sence of
index files would be gone to zero. In that case an index cache in
memory would be much better.
BTW: ADS 6.2 has checks on opening the table if they where built with
the same collation set.

> By the way, I am very content with the TAdsDelphiComponents.
> Should I reindex tables when moving them from one to another
> database??

Use 6.2 and set the AdsTable.IndexCollationMismatch property to
icmReIndex. That will do it automatically if built with a wrong
collation set.

--
Joachim Duerr
Lead ADS Support, Extended Systems GmbH, Germany
advantage[AT]extendsys.de
- posted with Xananews 1.15.6.2 -
!!! ADS 7 Beta now available !!!


Teunis Middelkoop Posted on 2003-08-30 15:50:25.0Z
Message-ID: <3F50C7C1.38808AE1@attglobal.net>
Date: Sat, 30 Aug 2003 11:50:25 -0400
From: Teunis Middelkoop <teunislc@attglobal.net>
Reply-To: teunislc@attglobal.net
Organization: Logical Connections Ltd.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD NSCPCD47 (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: Advantage.Delphi
Subject: Re: Locate
References: <3F4EA639.26A60B42@attglobal.net> <3f4ef92e@solutions.advantagedatabase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 32.105.11.159
X-Trace: 30 Aug 2003 09:21:03 -0700, 32.105.11.159
Lines: 41
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!32.105.11.159
Xref: solutions.advantagedatabase.com Advantage.Delphi:13822
Article PK: 1107258

Joachim,
Thanks for your help.
I have downloaded 6.2 and will implement it as soon as possible.
Teunis

"Joachim Duerr (ADS Support)" wrote:
>
> Teunis Middelkoop wrote in <3F4EA639.26A60B42@attglobal.net> :
>
> > A table (ADT and ADI) was copied from a CD to a database, controled by
> > ALS 6.11 The read only property was changed to archive.
> > In a program there is a call to the Locate function of the Table the
> > result is FALSE.
> > The table was reindexed and after that the locate works fine.
> > It worries me that the locate function does not give a warning like
> > index out of date, index corrupted or whatever.
> > I prefer rt errors above false results.
>
> If the ADT and the ADI came from the same location and it worked there
> before, I guess that you have different collation sequences set on the
> machines. If ADS would check logical index corruptions on opening the
> table, this would result in a huge performance loss and the sence of
> index files would be gone to zero. In that case an index cache in
> memory would be much better.
> BTW: ADS 6.2 has checks on opening the table if they where built with
> the same collation set.
>
> > By the way, I am very content with the TAdsDelphiComponents.
> > Should I reindex tables when moving them from one to another
> > database??
>
> Use 6.2 and set the AdsTable.IndexCollationMismatch property to
> icmReIndex. That will do it automatically if built with a wrong
> collation set.
>
> --
> Joachim Duerr
> Lead ADS Support, Extended Systems GmbH, Germany
> advantage[AT]extendsys.de
> - posted with Xananews 1.15.6.2 -
> !!! ADS 7 Beta now available !!!