Re: ADO corrupts date time values in where clause
- From: "sathya" <sathyagiri@xxxxxxxxx>
- Date: 20 Nov 2006 12:40:07 -0800
Thanks for looking into this though
Bob Barrows [MVP] wrote:
sathya wrote:
Thanks for your replies Bob.
Here's the actual code. Since this is a legacy application developed
in a language called OFB, not sure if it would make sense to you.
Anyways here's the code.
ADO SELECT FROM <TNAME> BECOMES <CONTEXTNAME> WHERE sno = 1;
ADO FINDFIRST <CONTEXTNAME> LOCK
ADO APPEND <CONTEXTNAME> col1 col2 col3
ADO UPDATE <CONTEXTNAME> UNLOCK
This is how the application code looks like.
You're right. I cannot help you with this.
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
.
- References:
- ADO corrupts date time values in where clause
- From: sathya
- Re: ADO corrupts date time values in where clause
- From: Bob Barrows [MVP]
- Re: ADO corrupts date time values in where clause
- From: sathya
- Re: ADO corrupts date time values in where clause
- From: Bob Barrows [MVP]
- Re: ADO corrupts date time values in where clause
- From: sathya
- Re: ADO corrupts date time values in where clause
- From: Bob Barrows [MVP]
- ADO corrupts date time values in where clause
- Prev by Date: Re: ADO corrupts date time values in where clause
- Next by Date: VBA ADO Connection to Oracle with Async
- Previous by thread: Re: ADO corrupts date time values in where clause
- Next by thread: Indexing of Connections
- Index(es):
Relevant Pages
|
|