t;[EMAIL PROTECTED]>
10/03/2005 23:37
Por favor, responda a
Axapta-Knowledge-Village@yahoogroups.com
Para
cc
Asunto
RE: RE: RE: RE: [Axapta-Knowledge-Village]
How can I find what RecId will be the next to be used?
Raul,
We had a problem with the COM
connector in th
@yahoogroups.com
Subject: RE: RE: RE: RE:
[Axapta-Knowledge-Village] How can I find what RecId will be the next to be
used?
Hi, Barry!!
I'd
like to do so, but the code is embedded in an huge Java program. I asked the
Java programmers to give me the part where we made the test, and it
54 PM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: Re: RE: RE: RE: [Axapta-Knowledge-Village] How can I find
what RecId will be the next to be used?
Yes, that solves the problem or duplicated
RecId's inserted in several tables, but doesn't solve the insert-error
issue...
R
AM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: Re: RE: RE:
[Axapta-Knowledge-Village] How can I find what RecId will be the next to be
used?
Preston ,
the problem isn't that records are inserted with same RecId, but Axapta doesn't
allow to do so!!
If I
de
IL PROTECTED]> escribió: -Para: De: "Preston A. Larimer" <[EMAIL PROTECTED]>Fecha: 04/03/2005 20:34Asunto: RE: RE: RE: [Axapta-Knowledge-Village] How can I find what RecId will be the next to be used?Definitely duplicate recID?s is not what you want, the menu path I gave you runs
: RE: RE:
[Axapta-Knowledge-Village] How can I find what RecId will be the next to be
used?
Preston, the
problem isn't that records are inserted with same RecId, but Axapta doesn't
allow to do so!!
If I deactivated the system-hidden indexes of many tables,
Axapta woul
uot;Preston A. Larimer" <[EMAIL PROTECTED]>Fecha: 03/03/2005 15:39Asunto: RE: RE: [Axapta-Knowledge-Village] How can I find what RecId will be the next to be used?Try Administration\Periodic\SQL Administration\Check Record Id?s(Button) -Preston Preston A. Larimer Professi
-Village@yahoogroups.com
Subject: Re: Re: RE:
[Axapta-Knowledge-Village] How can I find what RecId will be the next to be used?
We've tested this point until exhaustment.
The problem doesn't come when selecting or updating
records. The problem comes when we insert records co
can I find what RecId will be the next to be
used?
I've got a problem. Several users via COM, using same COM
session, sometimes invokes the error (Cannot insert a record in table X. The
record already exists). X may be an apparently alleatory table. And I need to
track so.
To
ECTED]> escribió: -Para: Axapta-Knowledge-Village@yahoogroups.comDe: "Karsten Krabbes" <[EMAIL PROTECTED]>Fecha: 03/03/2005 13:46Asunto: Re: RE: [Axapta-Knowledge-Village] How can I find what RecId will be the next to be used?Why don't you use the tablemethod exist() prio
Why don't you use the tablemethod exist() prior to creating the
record ?
Our problem seems not to be the recid. It seems the record is already
inserted into the table and needs to be updated
br
karsten
--- In Axapta-Knowledge-Village@yahoogroups.com, Raul Llorente
Peña/OPENSOLUTIONS <[EMAIL
álisis, Desarrollo e Implementación en Microsoft Bussiness Solutions-AxaptaOPEN SOLUTIONS-"Bayliss, Barry" <[EMAIL PROTECTED]> escribió: -Para: De: "Bayliss, Barry" <[EMAIL PROTECTED]>Fecha: 02/03/2005 23:57Asunto: RE: RE: [Axapta-Knowledge-Village] How can
February 2005
7:03 PM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: Re: RE:
[Axapta-Knowledge-Village] How can I find what RecId will be the next to be
used?
I've got a problem. Several users via COM, using same COM
session, sometimes invokes the error (Cannot insert a reco
I've got a problem. Several users via COM, using same COM session, sometimes invokes the error (Cannot insert a record in table X. The record already exists). X may be an apparently alleatory table. And I need to track so. Tool of log of database doesn't fit this...Raúl Llorente Peña Análisis
Of course, I DO really appreciate your attempts to help!! The fact, is I need to know EXACTLY what recId will be the next to be used. PS: the approach of inserting a "dummy" record in a "table" so its recid+1 will be the next one won't work (RECID's aren't neccessary linear and single directio
Well, do as you say... despite wichever method you use to read the SystemSequences Table, it will nearly always say you the record you will use!!! This is what I wanted to say. Debuggin, the only reference to global values are GlobalCache, but apparently there's no object like the table I will
Sorry David, but your appointment is invalid. When a user log into Axapta, the Kernel takes 25 recids into cache, and adds 25 to next value. Try yourself as below (create a table called T with a single string field called A): static void Job4(Args _args){ SystemSequences SS; T
17 matches
Mail list logo