G
Guest
Is it normal???
When adding a new record, via a form, as soon as the form goes dirty (user
keystroke) ADP/SQL Server goes out the underlying table to retrieve all
defaults defined for any column. It does this by calling the
sp_Mshelpcolumns procedure which is very costly.
For some tables it actually inhibits / interferes with the user entry. I
rarely use control default values however I assumed (or is that hope) that
table defaults would be applied at the server level and not the client level.
Is there anything I can do to eliminate/reduce this problem?
The form property has Fetch defaults as False. ADP 2003 (now SP2) Sql
Server 2k sp4.
I have looked online but have found little on the topic. Help me please!
When adding a new record, via a form, as soon as the form goes dirty (user
keystroke) ADP/SQL Server goes out the underlying table to retrieve all
defaults defined for any column. It does this by calling the
sp_Mshelpcolumns procedure which is very costly.
For some tables it actually inhibits / interferes with the user entry. I
rarely use control default values however I assumed (or is that hope) that
table defaults would be applied at the server level and not the client level.
Is there anything I can do to eliminate/reduce this problem?
The form property has Fetch defaults as False. ADP 2003 (now SP2) Sql
Server 2k sp4.
I have looked online but have found little on the topic. Help me please!