wow, this is a good one :(

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Single call to ExecuteNonQuery() with "EXECUTE MyAccessQuery" creates 86
new, identical records.

Here is the code from the Access Query
<AccessQueryCode>
INSERT INTO Tbl_ProtocolSegments ( ProtocolID, FreqBStart, FreqBEnd,
DurationSec, [Count], AmplitudeRampID, OpCode )
SELECT [_protocolID] AS Expr1, [_freqBStart] AS Expr2, [_freqBEnd] AS
Expr3, [_durationSec] AS Expr4, [_count] AS Expr5, [_amplitudeRampID] AS
Expr6, [_opCode] AS Expr7
FROM Tbl_ProtocolSegments;
</AccessQueryCode>

Here is the DAL code:
<DalCode>
m_command.CommandText = GetAccessSprocString(m_spInsertSegment);
m_command.Parameters.Clear();

OleDbParameter param = new OleDbParameter("_protocolID",
segment.ProtocolID);
m_command.Parameters.Add(param);

param = new OleDbParameter("_freqBStart", segment.Frequency2Start);
m_command.Parameters.Add(param);

param = new OleDbParameter("_freqBEnd", segment.Frequency2End);
m_command.Parameters.Add(param);

param = new OleDbParameter("_durationSec", segment.Duration);
m_command.Parameters.Add(param);

param = new OleDbParameter("_count", segment.Count);
m_command.Parameters.Add(param);

param = new OleDbParameter("_amplitudeRampID",
segment.AmplitudeRampValue);
m_command.Parameters.Add(param);

param = new OleDbParameter("_opCode", segment.OpCodeValue);
m_command.Parameters.Add(param);


// open the connection and execute the update
m_connection.Open();
m_command.ExecuteNonQuery();
<DalCode>


I have NO idea what is causing this. I have never seen something like this
before. Has anyone here seen this? Any ideas?

Thanks for reading!
Steve


.

Relevant Pages

  • Re: If you got to choose the syntax, what would you do?
    ... Except that CORE used the network address register in the on-chip ... When you write an opcode to a port it will either be executed directly ... it is going to execute or be treated as data. ...
    (comp.lang.forth)
  • Re: behavior of a 8086/88 encountering an illegal opcode
    ... "exception 6") behave when fed an illegal instruction opcode, ... 0Fh Opcode ... When the opcode 0Fh is encountered, the 8086,88 will execute a POP CS; ... The 8086,88 writes a byte at FFFFh and the next at offset ...
    (comp.lang.asm.x86)
  • Re: MSP430 post RETI behaviour
    ... > read about) will execute the opcode it returns to via its RETI ... And like in common market architectures, the highest interrupt source is serviced first and if you don't clear it, it is serviced immediatelly again. ... Other kind of behavior would imply that at least a line is carried out before servicing the interrupt. ...
    (comp.arch.embedded)
  • Re: "this" execution token?
    ... It becomes visible only at the end of compilation. ... execute \ execute the byte code from stack ... illegal opcode" cr abort ... Assuming you need an execute word in the jump table, perhaps it can be a safer one. ...
    (comp.lang.forth)
  • MSP430 post RETI behaviour
    ... read about) will execute the opcode it returns to via its RETI ... whether the interrupt mask is recoved from stack on or off? ... no hardware/cycle counting to do an NMI etc). ...
    (comp.arch.embedded)