Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem modifying usp to handle new data 1

Status
Not open for further replies.

PenelopeC

Technical User
May 12, 2003
72
US
Hi,
An Access97 app was written to parse a BTrieve db and import it into SQL every night. I did not create the application it was a now-long-gone consultant. He did a VERY nice job, but its time for the Btrieve to go.

I'm trying to keep the app pretty much the same, just accessing the same data from the new db. It is used to summarize work order amounts into accounting unit charges and aggregate equipment counts in order to internally charge customers (the data is formatted to go into a mainframe.)

I'm stuck on a stored procedure. When I run it in Query Analyzer it says "The command(s) completed successfully." However, if I run it from the Object Browser and enter a parameter, I get "Server: Msg 8624, Level 16, State 7, Procedure usp_eqf_get_charges_billable, Line 53
Internal SQL Server error."

I've looked all over for more meaning to the error but I can't find any further elaboration. When I use the debug function of QA I get "Server: Msg 8624, Level 16, State 7, Procedure usp_eqf_get_charges_billable, Line 54
[Microsoft][ODBC SQL Server Driver][SQL Server]Internal SQL Server error."

Does anyone know where I can get more info on this error message? Line 54 says "INSERT INTO [EQF_CHGS_BILLABLE]" but I know sometimes the errors are totally somewhere else.

Any help would be HUGELY appreciated, thanks!

Penelope

PenelopeC
~~~>-/O~~~~~swimming right along
 
From MS Knowledge Base:

SYMPTOMS
When a user deletes or updates a record in SQL Server, an internal error may be raised:

Server: Msg 8624, Level 16, State 1, Line 1
Internal SQL Server error.
An error message is returned to the client. No error message or access violation information is written to the SQL Server error logs. The record is not deleted or updated.
CAUSE
This error can only occur when a member table of an indexed view is updated or deleted and there is a DRI CASCADE constraint between the table and other tables in the view. Check to see if the table is defined with either a cascading delete or update constraint. Then check to see if there is a view with an index that depends on the tables.
RESOLUTION
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack



<bw>
"I swear by my life and my love of it that I will never live for the sake of another man, nor ask another man to live for mine."
— John Galt
Atlas Shrugged

If you want to get the best response to a question, please check out FAQ222-2244 first
 
Thank you....the knowledge base -- duh! I looked at BOL and it didn't tell me anything. I didn't even think about kb...<sigh> I guess my frustration kept me from thinking clearly!

Thank you again :D

PenelopeC
~~~>-/O~~~~~swimming right along
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top