Re: Table Defaults
- From: "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
- Date: Tue, 6 Nov 2007 15:00:44 -0500
In my test, I don't see the sp_MShelpcolumns called each a new record become
dirty; only for the first record created after the form is opened. More
important, this behavior doesn't seem to have any effect on the keystrokes;
ie. they don't get jumbled.
I suppose that you making some strange things in your code like playing with
the display.
Another possibility could be the Autocorrect option. If I were you, I would
deactivate all autocorrect options and see what this is giving.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"RJ" <RJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:57E1292A-265D-450E-A1B6-AA393C329414@xxxxxxxxxxxxxxxx
Yes, I understand what you are saying, but wouldn't that make the
property
DISPLAY DEFAULTS????
This following definition is from Microsoft
http://www.microsoft.com/mspress/books/sampchap/5600b.aspx
Fetch Defaults Choose Yes (the default) to have the form fetch the default
values from the field definitions when you move to a new row. Set this
property to No to use only the Default Value settings you have specified
for
controls.
My problem really has to do with the call to sp_Mshelpcolumns procedure
is
getting in the way of user entry. As the user types and the form becomes
dirty, the keystrokes get lost / jumbled. Franklin becomes nklinFa. Not
exactly user friendly. On most forms it is not a problem but on those more
complex forms with an underlying table with many columns it becomes an
issue.
One workaround is to redesign those lengthy tables but then that gets in
the
way bound forms / User interface which is the benefit of using Access as a
front end.
I have tested against a table that has no defaults and it doesn't seem to
matter.
I think I know where this is headed eventually. aka .Net
For some tables it actually inhibits
"Tom van Stiphout" wrote:
On Tue, 6 Nov 2007 05:27:00 -0800, RJ <RJ@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
It appears you assume FetchDefaults prevents the server call. However,
the help file says "Returns or sets a Boolean indicating whether
Microsoft Access SHOWS default values for new rows on the specified
form before the row is saved."
I'm reading this such that the call is always made, but the results
are optionally shown on the form.
-Tom.
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!
.
- Follow-Ups:
- Re: Table Defaults
- From: RJ
- Re: Table Defaults
- References:
- Re: Table Defaults
- From: Tom van Stiphout
- Re: Table Defaults
- From: RJ
- Re: Table Defaults
- Prev by Date: Re: SP in Subform Returns Empy Box for Some Users
- Next by Date: Re: Table Defaults
- Previous by thread: Re: Table Defaults
- Next by thread: Re: Table Defaults
- Index(es):
Relevant Pages
|
