Database Export Question

Hi All,
We have a procedure here we recently moved from Access 2000 to SQL Server
2000. Unfortunately, during the migration, we missed an export that is
needed (an index file). The prior indexes were stored in a CDX file. We
have a crystal reports routine running that needs this index file for proper
linking to a legacy app.
My question is "How can I export a CDX file to duplicate the results we had
from Access 2000?"
I hope someone here might have an answer and or another solution that might
work for me!
Thanks!
TravisTravis,
SQL Server does not use separate files for indexes. If you need a
particular index on a table in sql server you can generate one using CREATE
INDEX or you can use Enterprise Manager. If crystal is looking for this
file you might try a Crystal Reports news group or the Access newsgroup.
--
Andrew J. Kelly
SQL Server MVP
"REM7600" <rem7600@.hotmail.com> wrote in message
news:OhdiZjTgDHA.616@.TK2MSFTNGP11.phx.gbl...
> Hi All,
> We have a procedure here we recently moved from Access 2000 to SQL Server
> 2000. Unfortunately, during the migration, we missed an export that is
> needed (an index file). The prior indexes were stored in a CDX file. We
> have a crystal reports routine running that needs this index file for
proper
> linking to a legacy app.
> My question is "How can I export a CDX file to duplicate the results we
had
> from Access 2000?"
> I hope someone here might have an answer and or another solution that
might
> work for me!
> Thanks!
> Travis
>|||A CDX file is not a native Access 2000 file (unless it's simply a MDB file
that has been renamed).
Possibly you have a FoxPro database (DBF) linked into Access? FoxPro uses
the CDX file extension for its indexes.
> have a crystal reports routine running that needs this index file for
proper
> linking to a legacy app.
Presumably this routine is looking for a unqiue key which you can easily
create yourself either as a PRIMARY KEY or UNIQUE constraint or using CREATE
INDEX:
CREATE UNIQUE [NON]CLUSTERED INDEX...
See Books Online for details.
There should be no need to import the index itself because an index doesn't
contain any additional data, but if it is a FoxPro index then the Visual
FoxPro upsizing wizard would be an alternative method of recreating it in
SQL.
--
David Portas
--
Please reply only to the newsgroup
--|||Hey David,
I already have created the indexes in SQL Server but the Crystal app is not
recognizing these as being unique.
Thanks for the help. I'm gonna have to find another way areound this one...
Travis
> A CDX file is not a native Access 2000 file (unless it's simply a MDB file
> that has been renamed).
> Possibly you have a FoxPro database (DBF) linked into Access? FoxPro uses
> the CDX file extension for its indexes.
>
> > have a crystal reports routine running that needs this index file for
> proper
> > linking to a legacy app.
> Presumably this routine is looking for a unqiue key which you can easily
> create yourself either as a PRIMARY KEY or UNIQUE constraint or using
CREATE
> INDEX:
> CREATE UNIQUE [NON]CLUSTERED INDEX...
> See Books Online for details.
> There should be no need to import the index itself because an index
doesn't
> contain any additional data, but if it is a FoxPro index then the Visual
> FoxPro upsizing wizard would be an alternative method of recreating it in
> SQL.|||Hey Andrew,
I was afraid that was going to be the answer! OUCH! :-)
I already have the indexes created on the table so I guess I'll need to look
at doing it differently in Crystal. Oh, how these little projects grow...
:-) Thanks for the reply.
Travis
> SQL Server does not use separate files for indexes. If you need a
> particular index on a table in sql server you can generate one using
CREATE
> INDEX or you can use Enterprise Manager. If crystal is looking for this
> file you might try a Crystal Reports news group or the Access newsgroup.sql