Run-time Errors Occurring

[eugeniana]

The subject line makes it sound like a programming problem, but I really don't think it is.

I'm new to SQL Server and suddenly we have a user getting booted out, getting an incredible amount of run-time errors and having trouble saving into the table.

I've tried restoring, and ran the utility. Checked permissions and the table itself and the problem keeps getting worse. Does anyone have any other ideas?

I know, and extremely newbie question. But I really have no idea where to go from here. Thanks.

 

[mrdenny]

What's the exact error message that he's getting from the SQL Server. What utility are you referring to?

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[eugeniana]

Where to start? So far:

- Run-time error 2147217864 (80040e38): Row cannot be located from updating. Some valuess may have changed since it was last read.

- Run-time error 91: Object variable or width block variable not set.

- Run-time error 380: Invalid property.

- Run-time error 3704: Invalid permissions.

And that's just the ones she's turned in to me. I'm sure there's others she hasn't written down. It started about a month ago and picked up considerably in the last few days. Before that it was working perfectly, and I'm the only one with access to the database. I also know, for a fact, that I haven't touched the tables that seem to have problems since I inherited this portion of the position.

Utility run... Rebuild Master Utility.

 

[mrdenny]

That first one means that the program that she's using read the record, then she went to save a change to it, and during this time someone else has updated the record.

The second one is a programming error, probably related to data not comming back to the app as it is expecting.

The third one it probably the same as the second.

The fourth one could be a permissons error on the database, or on a network share, or even on her local drive.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[eugeniana]

But, wouldn't the second and third error be happening for every record then? Not just a select few?

On some it works right and on others she gets run-times.

 

[mrdenny]

No it all depends on the data comming back. It could be a null value being returned or a string that is to long, or a number that is to high or to low.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[eugeniana]

So what do you suggest?

 

[eugeniana]

Also, I guess we're getting a Record Could Not Save message.

 

[mrdenny]

Check your code in the program, and put some more error checking in where needed. I'm not sure how much help I can be since it's not a database problem.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[eugeniana]

Thanks! I appreciate the help you did give.

 

[mrdenny]

no problem, good luck with the programming folks.

Denny

--Anything is possible. All it takes is a little research. (Me)