Access ADO Form Insert Bug

Strange that a Resync command doesn't work well; as this should work in
every case.

Here an exemple of the dummy Resync command that I use:

CREATE PROCEDURE dbo.DummyResync (@p1 int, @p2 int, @p3 int, @p4 int, @p5
int)
AS
SELECT @p1, @p2, @p3, @p4, @p5
GO

and I call it this way:

DummyResync ?, ?, ?, ?, ?

The article referenced in your previous post says to use the following
syntax instead:

"{call CustordersResync (?)}"

but I didn't have the time to make a full analysis of this.

For the Profiler, click on File -- New -- Trace; then give the correct
connection parameters and click OK. After that, click on Run and you should
see a basic trace showing you all the commands sent by Access.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF


"Pete Nurse" wrote in message
ups.com...
Sylvain, thanks for the response.

1/ Yes, I use a single field primary key of type INT with identity set
(ie autonumber).

2/ As you suggest, I've tried entering a dummy Resynch command and it
seemed to overcome the reported problem, though I don't see how I can
enter "a SP
without the right number of parameters" without receiving an error. In
fact, it seems that entering a non-existent, nonsense SP name works
just as well (ie you get an error message). Could you please explain
how I can overcome that.

I tried entering the Resynch command as recommended at . . .

http://msdn.microsoft.com/library/de...ynccommand.asp

It seemed to work sometimes but not always. Certainly not as well
(apart from the error message) as the dummy SP idea.

3/ I had a look at Profiler, but it's pretty arcane - I have no idea
what I'm looking at.

Thanks for your response - maybe we're homing in on the solution.