There were problems in generating the linenum in Axapta 2.5.
The only thing you have to do is change the lienumbers to a correct
value.
As said in other group ... this process is done by axapta pre-
synchronize dataupgrade when updating from 2.5 to 3.0
br
karsten
--- In [EMAIL PROTECTED], <[EMAIL PROTECTED]>
wrote:
>
> you have a unique key violation.
>
> Start the SQL Administration in the Administration Menu. On all
Tables you can now "Check/Synchronize" your Tables. If you activate
all index options, you will be presented to all unique keys
violations. You can delete the duplicates.
>
> /Jesper
>
>
>
> -------- Original Message --------
> Subject: [development-axapta] infolog after database
synchronisation (05-Jul-2004 14:35)
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
>
> > hi all,
> >
> > after a database synchronisation i get an infolog whith:
> > " SQL-error: [Microsoft][ODBC SQL Server Driver][SQL Server]
CREATE
> > UNIQUE INDEX was closed, because .....SQL-statement: ALTER TABLE
> > PRODJOURNALROUTE ADD CONSTRAINT I_242LINEIDX PRIMARY KEY
CLUSTERED
> > (DATAAREAID,JOURNALID,LINENUM)"
> >
> > mostly i get this infolog, when i made an upgrade, for expamle a
new
> > servicepack, etc..
> >
> > so what is a good way to fix this error?
> >
> > best regards
> >
> > sascha g�ttler
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> > To: [EMAIL PROTECTED]
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
