_Excel_RangeRead until first blank row...

[FrancescoDiMuro]

Good morning guys, and Happy New Year!!! 

How are you? Hope fine I'm here because I'm trying to read an Excel sheet, until the function _Excel_RangeRead meet the first blank line... The issue is:
Even If I have cells without text, but formatted ( Cell Format: Text, Number... ), the function _Excel_RangeRead reads the "blank" cells, and I'd like to avoid this... What can I do in this case? Thanks everyone!

[FrancescoDiMuro]

Please, don't answer so many! 

[JLogan3o13]

@FrancescoDiMuro you need to show a little patience, you have been around long enough to know you need to wait 24 hours before bumping your posts.

[water]

Please check the wiki - section "Current Region" - and you will see how to do it.

[FrancescoDiMuro]

  On 1/4/2017 at 1:30 PM, water said:

Please check the wiki - section "Current Region" - and you will see how to do it.

Expand  

Thanks water. But how can I fix that? :/

[JLogan3o13]

Fix what? Did you read through the section you were pointed to?

[water]

If something goes wrong, please post the code you tried plus all error messages you get - or the result you expect vs. the result you get.

[FrancescoDiMuro]

I have an Excel sheet.
I want to read ONLY rows that are not empty.
 

Local $aRisultato = _Excel_RangeRead($oWorkbook, Default, $oWorkbook.ActiveSheet.Usedrange.Columns("A:H"), 1)

Using this, since I modifed some rows below the last NON EMPTY row, the function _Excel_RangeRead, reads those rows.
How can I DO NOT let the function read those rows?
Thanks

[FrancescoDiMuro]

  On 1/4/2017 at 1:41 PM, FrancescoDiMuro said:

I have an Excel sheet.
I want to read ONLY rows that are not empty.
 

Local $aRisultato = _Excel_RangeRead($oWorkbook, Default, $oWorkbook.ActiveSheet.Usedrange.Columns("A:H"), 1)

Using this, since I modifed some rows below the last NON EMPTY row, the function _Excel_RangeRead, reads those rows.
How can I DO NOT let the function read those rows?
Thanks

Expand  

My actual result:
A|B|C
1|2|3
Empty|Empty|Empty
My expected result:
A|B|C
1|2|3

[water]

I would simply read all rows and ignore the empty ones.

[FrancescoDiMuro]

  On 1/4/2017 at 1:47 PM, water said:

I would simply read all rows and ignore the empty ones.

Expand  

How? Something like this?
*After reading the entire sheet with the function I posted above...
 

Local $aNewRisultato
For $i = 2 To UBound($aRisultato) - 1
    If($aRisultato[$i][0]) <> "") Then
        $aNewRisultato = $aRisultato
    EndIf
Next
_ArrayDisplay($aNewRisultato)

 

[water]

About how many rows do we talk here?

[FrancescoDiMuro]

  On 1/4/2017 at 2:55 PM, water said:

About how many rows do we talk here?

Expand  

At the moment, not over 50... Maybe in the future, not over 150.
Ain't no fixed my issue :/
Thanks water...

[water]

In this case you could simply eliminate all blank rows:

For $i = UBound($aRisultato) - 1 To 2 Step -1 
    If $aRisultato[$i][0]) = "" Then _ArrayDelete($aRisultato, $i)
Next
_ArrayDisplay($aRisultato)

 

[FrancescoDiMuro]

  On 1/4/2017 at 3:07 PM, water said:

In this case you could simply eliminate all blank rows:

For $i = UBound($aRisultato) - 1 To 2 Step -1 
    If $aRisultato[$i][0]) = "" Then _ArrayDelete($aRisultato, $i)
Next
_ArrayDisplay($aRisultato)

 

Expand  

It works perfectly! Thanks water... But, why you do it in reverse? Just my curiosity  
PS: Now I'd like to develop the possibility to click on an item of the listeview and let a popup compares...

Edited January 4, 2017 by FrancescoDiMuro

[water]

Because you run into the following problem when doing it the other way round:

Imagine row 1 contains data, row 2 and 3 are empty, row 4 contains data. The script would do the following.

Check row 1 - is fine because it contains data - advance to row 2
Check row 2 - gets deleted because it is empty => now row 3 becomes row 2 - advance to row 3
Check row 3 ... wait! What happened to the former row 3 (which became row 2 as stated above)?

This approach would not process all records and crash when you reach the end of the array because the number of records in a for...next statement is only evaluated at the beginning. Later you would need to reduce this number because you delete records from the array.
It's still possible to use this approach but it becomes more complex

[FrancescoDiMuro]

  On 1/4/2017 at 3:27 PM, water said:

Because you run into the following problem when doing it the other way round:

Imagine row 1 contains data, row 2 and 3 are empty, row 4 contains data. The script would do the following.

Check row 1 - is fine because it contains data - advance to row 2
Check row 2 - gets deleted because it is empty => now row 3 becomes row 2 - advance to row 3
Check row 3 ... wait! What happened to the former row 3 (which became row 2 as stated above)?

This approach would not process all records and crash when you reach the end of the array because the number of records in a for...next statement is only evaluated at the beginning. Later you would need to reduce this number because you delete records from the array.
It's still possible to use this approach but it becomes more complex

Expand  

Ahhhhh, ok! Thanks for the explanation!  Really thanks, not as your "colleagues"... They seems to be angry with other people... By the way, I'd like to implementi an interesting thing... Read the PS of my previous post  Thanks!

[water]

No one is angry. You were simply pointed to the forum rules and the forum netiquette

Your new idea shouldn't be too hard to implement. Good luck

[FrancescoDiMuro]

  On 1/4/2017 at 3:35 PM, water said:

No one is angry. You were simply pointed to the forum rules and the forum netiquette

Your new idea shouldn't be too hard to implement. Good luck

Expand  

Thanks water, and have a good day!