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 |
DirkCIB
Starting Member
1 Post |
Posted - 2009-08-24 : 14:51:02
|
Hello, I am by no means anywhere close to being a SQL expert, so please remember this when responding to my message. I run a collection agency and am using a software system that uses SQL for their database. Unfortunately, the software company no longer exists, so I am on my own trying to troubleshoot problems. My problem is this: when a client adds new debtors to our system, they are stored in various tables in SQL. We have a 'posting' application that pulls them from SQL into our software system. Once the accounts are pulled in, they are supposed to be removed from SQL, but, mine are not. If I have four to pull in, only the first one pulls in, and the only one that does in fact pull in stays in the queue for the next time we post (along with the other 3 of course). So, I am having to go into Enterprise Manager and manually delete the one account that got pulled in. I have to continue to do this until all accounts are eventually pulled in. Would this have anything to do with SQL itself or the posting application that is being used? There is a postdebt.dll file that I know is integral in this procedure.Any help would be greatly appreciated. |
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2009-08-24 : 15:07:40
|
Probably the application, not the database causing this. Does the app log errors anywhere?You can run a profiler trace when you "pull in" the accounts and see what is getting executed at the SQL Server.Oh, and please STOP CALLING my house just kidding |
|
|
|
|
|
|
|