Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
blevine
Starting Member
2 Posts |
 Posted - 2008-01-30 : 17:48:34
|
| We are having all kinds of problems trying to run a relatively complex stored proc from an Access form against a SQL 2000 Server database. The program returns > 30,000 records and then tries to perform updates and inserts in other tables based on those 30,000+ returned records. The updates and inserts dont happen.If we run it where it returns 10,000 records it works fine.If we run it by highlighting the code and manually executing the code, it works fine. we think it might be some sort of timeout but we get no message or anything in a trace.Any ideas what the problem might be.ThanksBarrybarry@mcgnet.com |
|
|
Hommer
Aged Yak Warrior
808 Posts |
Posted - 2008-02-04 : 17:05:29
|
| You are exactly right.Access is not capable of handling a large number of data.Why don't you use some logic to filter it down?I don't think your users will have look through all 30K rows to conduct their business. |
 |
|
|
blevine
Starting Member
2 Posts |
Posted - 2008-02-06 : 15:48:41
|
| We are importing very large spreadsheets of royalty data. It lists ringtones and songs that were played. Once imported, its processed for payment. Only the few columns that dont 'match' our database of valid songs need to be manually reviewed. The problem is that instead of 90% of the rows properly matching, only 10% are matching because of some failure somewhere in the import. The only solution so far is to run it as a stored proc in a DTS package but its a little harder to monitor and debug and it still has its kinks.Any other ideas? |
|
|
|
|
|
|
Access front end - SQL backend limitations