We have a universe setup with MS SQL Server as the backend database. Some of the corporate users would like to run various reports for a subset of accounts.
There are approximately 20,000 accounts.
We would like to be able to create a list of 300 - 400 accounts in a text file or an Excel spreadsheet
and have the report run for only those accounts. We could enter the account numbers in a single column of an Excel spreadsheet. We would need to set a join condition on
the account number in the SQL Table (BO Class) to the Excel spreadsheet.
We were able to get it working if the list in the external source was small (3 accounts),
but when I tried it with 200 accounts, it produced a buffer overflow error.
What is the best way to achieve our goal of running the report for a subset of accounts?
Thank You,
Barry KornReich
********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. **********************************************************************
At 01:05 PM 3/23/2000 -0500, Barry KornReich wrote:
We would like to be able to create a list of 300 - 400 accounts in a text file or an Excel spreadsheet
and have the report run for only those accounts.
but when I tried it with 200 accounts, it produced a buffer overflow error.
What is the best way to achieve our goal of running the report for a subset of accounts?
Barry, why not put the accounts in a table, and restrict based on the join?
I agree with Anita. We set up a process where a user can click on an icon which ftp’s a text file which contains a list of account numbers and a “pool id” to our database server. We then have a procedure which loads that file into a table in the database. This “pool id” is an object in the universe for the users to use in their selection criteria. It works very well and the warehouse team generally doesn’t even have to get involved. It’s all under the user’s control.
Barry, why not put the accounts in a table, and restrict based on the join?
Personally I would not approach your problem this way. I would instead have a single table in SQL that has each and every account in that table. I would then put a column on the table to indicate the groupings (i.e. set 1, set 2 etc.). I would then use a subquery to bring back the list of the accounts.
Just a suggestion…
Simon