Re: Baffled by bug (?) in SqlCeCommand:
- From: Matt <usenet.junk.000@xxxxxxxxx>
- Date: Tue, 29 Apr 2008 08:32:39 -0700
"Ginny Caughey MVP" <ginny.caughey.online@xxxxxxxxxxxxxx> wrote in
news:8D995E95-5DA4-4507-94B5-9C1FA7D28EEF@xxxxxxxxxxxxx:
Matt,
Have you tried clearing the parmaters to the command, then adding back
the paramter for the new date?
Ginny
Sounded promising, I tried it and it didn't fix.
What did work was toggling the connection for the cmd object:
_sqlcmdGetDTitlesAndNewByTargetDate.Connection = null;
_sqlcmdGetDTitlesAndNewByTargetDate.Connection = _sqlConn;
I've put this at the end of the save-new-entry routine and it fixes the
bug. Ugly, but it works.
Thanks for the suggestion. Set me on the right track and at least let me
know I wasn't missing something obvious (I'm new to SqlCE).
Matt
<snip me explaining the bizarre ignore-WHERE-clause scenario>
.
- Follow-Ups:
- Re: Baffled by bug (?) in SqlCeCommand:
- From: Ginny Caughey MVP
- Re: Baffled by bug (?) in SqlCeCommand:
- References:
- HELP: Baffled by bug (?) in SqlCeCommand:
- From: Matt
- Re: Baffled by bug (?) in SqlCeCommand:
- From: Ginny Caughey MVP
- HELP: Baffled by bug (?) in SqlCeCommand:
- Prev by Date: Re: HELP: Baffled by bug (?) in SqlCeCommand:
- Next by Date: Re: Baffled by bug (?) in SqlCeCommand:
- Previous by thread: Re: Baffled by bug (?) in SqlCeCommand:
- Next by thread: Re: Baffled by bug (?) in SqlCeCommand:
- Index(es):
Relevant Pages
|
Loading