Hi Paul
You are probably well past this by now but I only just got your reply.
I have never worked with Oracle so I don't have the specific knowledge.
However:
My logic was that the dynaset is a collection of collections. It is a
collection of records and the records are a collection of fields.
to my mind the Dynaset("FileDate") may be ambiguous. It may be looking for
a Filedate Record in the records collection or it may be looking for a
field in the current record. I know generally a dynaset tries to work with
the current record but I always prefer to overspecify if there is any doubt
(or things don't work).
It looked a bit like saying x=worksheet("Sheet1").value to me.
Anyhow it looks like a minor change has caused you some recoding. Good
luck!
Regards
David Grugeon
Regards
David Grugeon
On 29 January 2013 07:06, Paul Schreiner <schreiner_p...@att.net> wrote:
> David,
>
> thanks!
> literally 5 minutes ago, I came across a posting on Oracle's forum
> where a user recommended using:
>
> TDate = Dynaset("filedate").Value.ToDate
>
> which worked.
> It's odd that the timestamp field type came out in v9.2 (I think)
> and "= Dynaset("filedate").Value" worked in v10i, but now does not in
> v11.2...
>
> I THINK it may be an issue with the fact that they've incorporated
> a Time Zone portion with the TimeStamp field type.
>
> Your solution is interesting though.
> it actually returns a class object.
>
> Where the DB value was "31-Mar-1999 12:00:00 AM"
> tDate = Dynaset.fields("filedate") returned:
>
> TDate.Day : Long: 31
> TDate.format : String: "DD-MON-RR HH.MI.SSXFF AM"
> TDate.Hour : Long: 0
> TDate.Minute : Long: 0
> TDate.Month : Long: 3
> TDate.Nanosecond : Long: 0
> TDate.Second : Long: 0
> TDate.Value : String : "31-MAR-99 12.00.00.000000000 AM"
> TDate.Year : Long: 1999
>
> in which case TDate.Value is a valid value of: "31-MAR-99
> 12.00.00.000000000 AM"
> but tStr = Dynaset("FileDate").Value
> returned an error.
> very curious...
>
> and the possibilities...
>
> much to think about...
> AFTER I search through 80,000 lines of code and find where I may be
> referencing a timestamp field...
> (sigh)
>
> thanks for your help!
>
>
> *Paul*
>
> -----------------------------------------
> *“Do all the good you can,
> By all the means you can,
> In all the ways you can,
> In all the places you can,
> At all the times you can,
> To all the people you can,
> As long as ever you can.” - John Wesley
> *-----------------------------------------
>
>
> ------------------------------
> *From:* David Grugeon <da...@grugeon.com.au>
> *To:* "excel-macros@googlegroups.com" <excel-macros@googlegroups.com>
> *Sent:* Mon, January 28, 2013 3:07:29 PM
> *Subject:* Re: $$Excel-Macros$$ Oracle 11.2 client problem with timestamp
> object
>
> Hi Paul
> Try
>
> Dynaset.fields("filedate")
>
> On Tuesday, 29 January 2013, Paul Schreiner wrote:
>
>> I recently had my computer upgraded.
>> My old computer (which I still can switch to) had the Oracle 9.2 client
>> installed.
>> I have an Oracle table that looks like this:
>> Name Type
>> ----------- ------------
>> ARCHNAME VARCHAR2(17)
>> FILEDATE TIMESTAMP(6)
>> FILESIZE NUMBER(10)
>> FILENAME VARCHAR2(200)
>> FULLNAME VARCHAR2(500)
>> UPPERNAME VARCHAR2(500)
>> COMMITAR VARCHAR2(4)
>>
>> A "snippet" of my code looks like:
>>
>> Set OraSession = CreateObject("OracleInProcServer.XOraSession")
>> Set OraDatabase = OraSession.OpenDatabase("PMFD", "userid/password",
>> 1&)
>>
>> SQLStmt = "Select filedate from mfgdesowner.find_files where uppername
>> like '%1509423%' "
>>
>> Set Dynaset = OraDatabase.DbCreateDynaset(SQLstmt, 0&)
>> If (Dynaset.RecordCount > 0) Then
>> For I = 1 To Dynaset.RecordCount
>> RepCnt = RepCnt + 1
>> Debug.Print Dynaset("filedate").Value
>> Dynaset.Movenext
>> Next I
>> Endif
>>
>> But, I get an error or the Dynaset("filedate").Value statement.
>> Specifically:
>>
>> "438: Object doesn't support this property or method"
>>
>> and it throws me out of the function.
>>
>> The code has run for many, many years.
>>
>> Well... technically, the table USED to have separate date/time fields.
>>
>> When Oracle came out with the TimeStamp field, I redesigned my
>> applications to make use of it.
>>
>> Has anyone experienced this problem and know how to fix it?
>>
>> thank you!
>>
>> Paul
>>
>>
>> --
>> Join official Facebook page of this forum @
>> https://www.facebook.com/discussexcel
>>
>> FORUM RULES
>>
>> 1) Use concise, accurate thread titles. Poor thread titles, like Please
>> Help, Urgent, Need Help, Formula Problem, Code Problem, and Need Advice
>> will not get quick attention or may not be answered.
>> 2) Don't post a question in the thread of another member.
>> 3) Don't post questions regarding breaking or bypassing any security
>> measure.
>> 4) Acknowledge the responses you receive, good or bad.
>> 5) Jobs posting is not allowed.
>> 6) Sharing copyrighted material and their links is not allowed.
>>
>> NOTE : Don't ever post confidential data in a workbook. Forum owners and
>> members are not responsible for any loss.
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "MS EXCEL AND VBA MACROS" group.
>> To post to this group, send email to excel-macros@googlegroups.com.
>> To unsubscribe from this group, send email to
>> excel-macros+unsubscr...@googlegroups.com.
>> Visit this group at http://groups.google.com/group/excel-macros?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>
> --
> Regards
> David Grugeon
>
> --
> Join official Facebook page of this forum @
> https://www.facebook.com/discussexcel
>
> FORUM RULES
>
> 1) Use concise, accurate thread titles. Poor thread titles, like Please
> Help, Urgent, Need Help, Formula Problem, Code Problem, and Need Advice
> will not get quick attention or may not be answered.
> 2) Don't post a question in the thread of another member.
> 3) Don't post questions regarding breaking or bypassing any security
> measure.
> 4) Acknowledge the responses you receive, good or bad.
> 5) Jobs posting is not allowed.
> 6) Sharing copyrighted material and their links is not allowed.
>
> NOTE : Don't ever post confidential data in a workbook. Forum owners and
> members are not responsible for any loss.
> ---
> You received this message because you are subscribed to the Google Groups
> "MS EXCEL AND VBA MACROS" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to excel-macros+unsubscr...@googlegroups.com.
>
> To post to this group, send email to excel-macros@googlegroups.com.
> Visit this group at http://groups.google.com/group/excel-macros?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
> --
> Join official Facebook page of this forum @
> https://www.facebook.com/discussexcel
>
> FORUM RULES
>
> 1) Use concise, accurate thread titles. Poor thread titles, like Please
> Help, Urgent, Need Help, Formula Problem, Code Problem, and Need Advice
> will not get quick attention or may not be answered.
> 2) Don't post a question in the thread of another member.
> 3) Don't post questions regarding breaking or bypassing any security
> measure.
> 4) Acknowledge the responses you receive, good or bad.
> 5) Jobs posting is not allowed.
> 6) Sharing copyrighted material and their links is not allowed.
>
> NOTE : Don't ever post confidential data in a workbook. Forum owners and
> members are not responsible for any loss.
> ---
> You received this message because you are subscribed to the Google Groups
> "MS EXCEL AND VBA MACROS" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to excel-macros+unsubscr...@googlegroups.com.
>
> To post to this group, send email to excel-macros@googlegroups.com.
> Visit this group at http://groups.google.com/group/excel-macros?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
Join official Facebook page of this forum @
https://www.facebook.com/discussexcel
FORUM RULES
1) Use concise, accurate thread titles. Poor thread titles, like Please Help,
Urgent, Need Help, Formula Problem, Code Problem, and Need Advice will not get
quick attention or may not be answered.
2) Don't post a question in the thread of another member.
3) Don't post questions regarding breaking or bypassing any security measure.
4) Acknowledge the responses you receive, good or bad.
5) Jobs posting is not allowed.
6) Sharing copyrighted material and their links is not allowed.
NOTE : Don't ever post confidential data in a workbook. Forum owners and
members are not responsible for any loss.
---
You received this message because you are subscribed to the Google Groups "MS
EXCEL AND VBA MACROS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to excel-macros+unsubscr...@googlegroups.com.
To post to this group, send email to excel-macros@googlegroups.com.
Visit this group at http://groups.google.com/group/excel-macros?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
