Article View: borland.public.vdbase.data.sql
Article #1502Re: Problem with Order Tag on SQL Tables
From: Ken Chan
Date: Wed, 17 Dec 1997 00:00
Date: Wed, 17 Dec 1997 00:00
20 lines
1032 bytes
1032 bytes
Garth Wells wrote: > The documentation says you can specify the Order Tag on a SQL Table, but I > get the TAG NOT FOUND error every time I try. This might be server-dependent, and there may be something goofy with the names with MS-SQL. Using the sample Employee database in Interbase, I was able to: use CUSTOMER display status // See CUSTREGION as an index tag use CUSTOMER order CUSTREGION display status // See CUSTREGION as current Master index So at least it's working with Interbase. -- //Ken[0]@Borland <Please follow-up to newsgroup; do not reply to email>
Technical Details
Message-ID:
<MPG.f01fde638bbf0e98975b@forums.borland.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<01bd0a7b$56007e50$74ffc2d0@wells>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: ff5a1,3ddd9c9af1c9a349 X-Google-Attributes: gidff5a1,public From: supportinfo@borland.com (Ken Chan) Subject: Re: Problem with Order Tag on SQL Tables Date: 1997/12/17 Message-ID: <MPG.f01fde638bbf0e98975b@forums.borland.com> X-Deja-AN: 299167203 References: <01bd0a7b$56007e50$74ffc2d0@wells> Organization: Borland Newsgroups: borland.public.vdbase.data.sql