hello, question of performance:
can I import an Excel document of 10.000 lines in same a view ?
if it is not advised i.e. if the application becomes very slow is what it would be better to leave the data on Excel is to make accés for each operation (search, addition, delete or of the statistics)
if there are other proposals do not hesitate
Thank you in advance
Subject: performance question: 10.000 lines from excel in the same view
Notes cannot import an Excel worksheet directly. The only spreadsheet format supported by Notes is (surprise surprise) Lotus 1-2-3. 1-2-3 supports only 8,192 rows, so even if you were to save your XL worksheet as .WK3, you’re going to have a few thousand rows truncated.
The other alternative is to save your worksheet as either a delimited or fixed record length text file and importing that.
Subject: performance question: 10.000 lines from excel in the same view
I go well on developing a program domino which import from Excel I ask you which are the amiliorations that they is necessary to bring to the application so that it functions correctly
either to leave the base on Excel is to make access for each operation
either to import of piece, or to find another ideas to import all the base
Thank you
Subject: performance question: 10.000 lines from excel in the same view
Let me restate to see if I understand your question.You have an Excel file of about 10000 rows.
You need to use the Excel file data in a Notes app.
You want to know if it is faster to
Import the Excel file (I’m assuming you’re using OLE for this) and then work ‘all Notes’ or
Use OLE (or ODBC maybe?) to find and use data directly from Excel as needed.
If the Excel data changes infrequently, and is used a lot by the Notes app, I’d tend to bring it into Notes and use it there - the OLE import isn’t going to be terribly fast, but once it’s into Notes, everything else works quickly.
If the Excel data changes a lot, or is used infrequently, you may want to leave it in Excel and read/modify it only as required.
You don’t provide much information about your application need so it’s rather difficult to provide any kind of ‘good’ answer.
Also - both options are easy to test. Why not just build the code both ways and see what works best? Nothing like a good experiment to help you decide!
HTH
Doug