Raul,
We had a problem with the COM connector in
the past. We found that you were unable to completely close a COM connection
(you had to exit the application in order for the COM to close correctly, as
recognised by Axapta). As a result, we had to rewrite the code to use 1 COM
connection per application (otherwise we would run out of COM licenses).
In the end, we rewrote the code to use a
server/daemon application, hence only using 1 COM connection.
How many COM connection calls are made in
the Java code?
How many COM licenses do you have?
Is there a reason that all inserts need to
occur at the same time?
Now that you have run the process
suggested by Preston, what
error are you receiving?
Barry.
From:
Raul Llorente Peña/OPENSOLUTIONS [mailto:[EMAIL PROTECTED]
Sent: Thursday, 10 March 2005 7:16
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?
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's huge,
however. Basically, it opens several COM sessions, and open a test table, and inserts
100 records in it. There's a start&sinchronization time for the loops that
makes the insert, so all COM sessions (and insert loop subprocesses) begin at
same time. That's that way we discovered the error.
And
now I'm not physically in the customer that have that problem, so until next
week I can't post it. You want it, however?
Raúl
Llorente Peña
Análisis, Desarrollo e Implementación en
Microsoft Bussiness Solutions-Axapta
OPEN SOLUTIONS
|
"Bayliss, Barry"
<[EMAIL PROTECTED]>
09/03/2005 23:43
|
Por
favor, responda a
Axapta-Knowledge-Village@yahoogroups.com
|
|
|
Para
|
<Axapta-Knowledge-Village@yahoogroups.com>
|
|
cc
|
|
|
Asunto
|
RE: RE: RE: RE: [Axapta-Knowledge-Village] How
can I find what RecId will be the next to be used?
|
|
Raul,
Are you able to post the code that generates the error?
Barry.
From: Raul Llorente
Peña/OPENSOLUTIONS [mailto:[EMAIL PROTECTED]
Sent: Sunday, 6 March 2005 6: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...
Raúl
Llorente Peña
Análisis, Desarrollo e Implementación en
Microsoft Bussiness Solutions-Axapta
OPEN SOLUTIONS
-----"Preston A. Larimer"
<[EMAIL PROTECTED]> escribió: -----
Para: <Axapta-Knowledge-Village@yahoogroups.com>
De: "Preston A. Larimer" <[EMAIL PROTECTED]>
Fecha: 04/03/2005 20:34
Asunto: 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 the check on recids for all of your tables and corrects
issues with them being duplicated, or the SystemSequences being out of kilter,
every time Axapta has throw up the unable to insert record due to a duplicate
caused by the recID, via com or standard Axapta this process has fixed my
problem.
Hope it helps you.
-Preston
From: Raul Llorente
Peña/OPENSOLUTIONS [mailto:[EMAIL PROTECTED]
Sent: Friday, March 04, 2005 3:25 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 deactivated the system-hidden indexes of many tables, Axapta would allow
it... until next sinchronization!! And remember, there are several tables based
on refRecId field and similar, so possibility of incoherence if I allow to
insert duplicated RecIds looks dangerous...
Raúl
Llorente Peña
Análisis, Desarrollo e Implementación en
Microsoft Bussiness Solutions-Axapta
OPEN SOLUTIONS
-----"Preston A. Larimer" <
[EMAIL PROTECTED] > escribió: -----
Para : < Axapta-Knowledge-Village@yahoogroups.com
>
De: "Preston A. Larimer" < [EMAIL PROTECTED] >
Fecha: 03/03/2005 15:39
Asunto: 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
Professional Solutions Group, LLC
[EMAIL PROTECTED]
www.psgroupllc.com
-------------------------------------------------------------------------------------
Building a stronger link in the Axapta community chain, join us at
From: Raul Llorente
Peña/OPENSOLUTIONS [mailto:[EMAIL PROTECTED]
Sent: Friday, February 25, 2005 4:03 AM
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 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, Desarrollo e Implementación en
Microsoft Bussiness Solutions-Axapta
OPEN SOLUTIONS
-----"Bayliss, Barry"
<[EMAIL PROTECTED]> escribió: -----
Para : < Axapta-Knowledge-Village@yahoogroups.com
>
De: "Bayliss, Barry" <[EMAIL PROTECTED]>
Fecha: 24/02/2005 23:26
Asunto: RE: [Axapta-Knowledge-Village] How can I find what RecId will be the
next to be used?
Hello Raul,
Why is it that you need to find the recID for before the
insertion?
Barry.
From: Raul Llorente
Peña/OPENSOLUTIONS [mailto:[EMAIL PROTECTED]
Sent: Thursday, 24 February 2005 3:08 AM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: [Axapta-Knowledge-Village] How can I find what RecId will
be the next to be used?
How
can I find what RecId will be the next to be used, before inserting a record
and without accessing the table of RecIds (SystemSequences)?
Raúl
Llorente Peña
Análisis, Desarrollo e Implementación en
Microsoft Bussiness Solutions-Axapta
OPEN SOLUTIONS
Sharing the knowledge on Axapta.
Sharing the knowledge on Axapta.
Sharing the knowledge on Axapta.
Sharing the knowledge on Axapta.
Sharing the knowledge on Axapta.
Sharing the knowledge on Axapta.
Sharing the knowledge on Axapta.
Sharing the knowledge on Axapta.
Yahoo! Groups Links
Sharing
the knowledge on Axapta.
Sharing the knowledge on Axapta.
| Yahoo! Groups Sponsor |
ADVERTISEMENT
![click here]() | |
![]() |
Yahoo! Groups Links
