The Origin Forum
File Exchange
Try Origin for Free
The Origin Forum
Home | Profile | Register | Active Topics | Members | Search | FAQ | Send File to Tech support
 All Forums
 Origin Forum for Programming
 Forum for Origin C
 GetNumRows() behavior after database import

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Screensize:
UserName:
Password:
Anti-Spam Code:
Format Mode:
Format: BoldItalicizedUnderlineStrikethrough Align LeftCenteredAlign Right Horizontal Rule Insert HyperlinkUpload FileInsert Image Insert CodeInsert QuoteInsert List
   
Message:

* HTML is OFF
* Forum Code is ON
Smilies
Smile [:)] Big Smile [:D] Cool [8D] Blush [:I]
Tongue [:P] Evil [):] Wink [;)] Clown [:o)]
Black Eye [B)] Eight Ball [8] Frown [:(] Shy [8)]
Shocked [:0] Angry [:(!] Dead [xx(] Sleepy [|)]
Kisses [:X] Approve [^] Disapprove [V] Question [?]

 
Check here to subscribe to this topic.
   

T O P I C    R E V I E W
aplotnikov Posted - 03/15/2017 : 11:58:13 AM
Origin Ver. and Service Release (Select Help-->About Origin): 8.6 SR3 64-bit
Operating System: Win 7 Pro SP1 64-bit

Hello,

I employ PutRecordset/ReadRecordset functions to import data from SQL databases - everything works fine. However if I try to get the worksheet row number by means Worksheet::GetNumRows function afterwards, it returns always the value of 30 if the number of rows is less than 30. Of course, the problem can be easily solved by means of Dataset::GetSize function, but I'm just curious, whether this limitation of GetNumRows is deliberate.

Regards,

Alexei
1   L A T E S T    R E P L I E S    (Newest First)
cpyang Posted - 03/15/2017 : 7:36:30 PM
Origin Worksheet GetNumRows is looking at the currently allocated space, and since each column can potentially have different number of values, you do need to look at individual column to get the actual size. So either Dataset GetSize, of get Column and call GetUpperBound.

CP

The Origin Forum © 2020 Originlab Corporation Go To Top Of Page
Snitz Forums 2000