I've decided to move as much into sql as possible for one of the subsystems of an application and I want to trap INSERT and UPDATE queries for inappropriate data (eg strings to long) and locking problems.

I started by trying to stuff 80 bytes into a VARCHAR(5) field using INSERT. An error message is generated but TEDBQuery's events (well the three I tried anyway) aren't triggered.

I'm hoping there's a way to trap problems when using a query and I'm just to thick to see it. Help anyone?

Roy Lambert

Roy,

<< I've decided to move as much into sql as possible for one of the subsystems of an application and I want to trap INSERT and UPDATE queries for inappropriate data (eg strings to long) and locking problems.

I started by trying to stuff 80 bytes into a VARCHAR(5) field using INSERT. An error message is generated but TEDBQuery's events (well the three I tried anyway) aren't triggered.

I'm hoping there's a way to trap problems when using a query and I'm just to thick to see it. Help anyone? >>

SQL execution errors are simply raised as exceptions, so you would just use normal exception handling techniques to deal with them.  Either that, or use a database procedure and trap/handle the exception there.

Tim Young
Elevate Software
www.elevatesoft.com

Tim


>SQL execution errors are simply raised as exceptions, so you would just use normal exception handling techniques to deal with them. Either that, or use a database procedure and trap/handle the exception there.

I was hoping to avoid another layer of try..except. I think I'll override ExecSQL in my subclassed query and add it in there.

Roy