I've got a form based on a sql server table, the recordsource is
   select * from table where id = foo

the form has textboxes, combo boxes - nothing special

I periodically get error
   Operation is not supported for this type of object. ,DAO.Fields ,
3251

when clicking a command button that does
    if me.dirty then
         me.dirty = false
    endif


the beforeUpdate event just checks that certain fields are filled in,
popping up a message and setting cancel=true

this was not occurring with access97, does anyone have an idea as to
why this is happening ?

On Sep 3, 6:36=A0am, Roger <lesperan...@natpro.com> wrote:
> I've got a form based on a sql server table, the recordsource is
> =A0 =A0select * from table where id =3D foo
>
> the form has textboxes, combo boxes - nothing special
>
> I periodically get error
> =A0 =A0Operation is not supported for this type of object. ,DAO.Fields ,
> 3251
>
> when clicking a command button that does
> =A0 =A0 if me.dirty then
> =A0 =A0 =A0 =A0 =A0me.dirty =3D false
> =A0 =A0 endif
>
> the beforeUpdate event just checks that certain fields are filled in,
> popping up a message and setting cancel=3Dtrue
>
> this was not occurring with access97, does anyone have an idea as to
> why this is happening ?

Sounds kind of like a reference problem to me.  Check and make sure
they're all there and nothing's marked "Missing".  Also make sure DAO
is above ADO if you haven't specifically stated that an object is one
or the other.

On Sep 5, 8:48=A0am, Chuck Grimsby <cgat...@gmail.com> wrote:
> On Sep 3, 6:36=A0am, Roger <lesperan...@natpro.com> wrote:
>
>
>
>
>
> > I've got a form based on a sql server table, the recordsource is
> > =A0 =A0select * from table where id =3D foo
>
> > the form has textboxes, combo boxes - nothing special
>
> > I periodically get error
> > =A0 =A0Operation is not supported for this type of object. ,DAO.Fields =
,
> > 3251
>
> > when clicking a command button that does
> > =A0 =A0 if me.dirty then
> > =A0 =A0 =A0 =A0 =A0me.dirty =3D false
> > =A0 =A0 endif
>
> > the beforeUpdate event just checks that certain fields are filled in,
> > popping up a message and setting cancel=3Dtrue
>
> > this was not occurring with access97, does anyone have an idea as to
> > why this is happening ?
>
> Sounds kind of like a reference problem to me. =A0Check and make sure
> they're all there and nothing's marked "Missing". =A0Also make sure DAO
> is above ADO if you haven't specifically stated that an object is one
> or the other.- Hide quoted text -
>
> - Show quoted text -

I checked, no missing references
using only DAO

On Sep 3, 7:36=A0am, Roger <lesperan...@natpro.com> wrote:
> I've got a form based on a sql server table, the recordsource is
> =A0 =A0select * from table where id =3D foo
>
> the form has textboxes, combo boxes - nothing special
>
> I periodically get error
> =A0 =A0Operation is not supported for this type of object. ,DAO.Fields ,
> 3251
>
> when clicking a command button that does
> =A0 =A0 if me.dirty then
> =A0 =A0 =A0 =A0 =A0me.dirty =3D false
> =A0 =A0 endif
>
> the beforeUpdate event just checks that certain fields are filled in,
> popping up a message and setting cancel=3Dtrue
>
> this was not occurring with access97, does anyone have an idea as to
> why this is happening ?

This is a shot in the dark.  Did you turn off Name AutoCorrect and
apply any available Service Packs?  That guess is based on an old KB
article and its advice:

http://support.microsoft.com/kb/247488

James A. Fortune
CDMAPoster@FortuneJames.com

On Sep 7, 8:14=A0am, "James A. Fortune" <CDMAPos...@FortuneJames.com>
wrote:
> On Sep 3, 7:36=A0am, Roger <lesperan...@natpro.com> wrote:
>
>
>
>
>
> > I've got a form based on a sql server table, the recordsource is
> > =A0 =A0select * from table where id =3D foo
>
> > the form has textboxes, combo boxes - nothing special
>
> > I periodically get error
> > =A0 =A0Operation is not supported for this type of object. ,DAO.Fields =
,
> > 3251
>
> > when clicking a command button that does
> > =A0 =A0 if me.dirty then
> > =A0 =A0 =A0 =A0 =A0me.dirty =3D false
> > =A0 =A0 endif
>
> > the beforeUpdate event just checks that certain fields are filled in,
> > popping up a message and setting cancel=3Dtrue
>
> > this was not occurring with access97, does anyone have an idea as to
> > why this is happening ?
>
> This is a shot in the dark. =A0Did you turn off Name AutoCorrect and
> apply any available Service Packs? =A0That guess is based on an old KB
> article and its advice:
>
> http://support.microsoft.com/kb/247488
>
> James A. Fortune
> CDMAPos...@FortuneJames.com- Hide quoted text -
>
> - Show quoted text -

I checked both, and yes,
   name autocorrect is off
   service pack is current

On Sep 7, 3:06=A0pm, Roger <lesperan...@natpro.com> wrote:
> On Sep 7, 8:14=A0am, "James A. Fortune" <CDMAPos...@FortuneJames.com>
> wrote:
>
>
>
>
>
> > On Sep 3, 7:36=A0am, Roger <lesperan...@natpro.com> wrote:
>
> > > I've got a form based on a sql server table, the recordsource is
> > > =A0 =A0select * from table where id =3D foo
>
> > > the form has textboxes, combo boxes - nothing special
>
> > > I periodically get error
> > > =A0 =A0Operation is not supported for this type of object. ,DAO.Field=
s ,
> > > 3251
>
> > > when clicking a command button that does
> > > =A0 =A0 if me.dirty then
> > > =A0 =A0 =A0 =A0 =A0me.dirty =3D false
> > > =A0 =A0 endif
>
> > > the beforeUpdate event just checks that certain fields are filled in,
> > > popping up a message and setting cancel=3Dtrue
>
> > > this was not occurring with access97, does anyone have an idea as to
> > > why this is happening ?
>
> > This is a shot in the dark. =A0Did you turn off Name AutoCorrect and
> > apply any available Service Packs? =A0That guess is based on an old KB
> > article and its advice:
>
> >http://support.microsoft.com/kb/247488
>
> > James A. Fortune
> > CDMAPos...@FortuneJames.com- Hide quoted text -
>
> > - Show quoted text -
>
> I checked both, and yes,
> =A0 =A0name autocorrect is off
> =A0 =A0service pack is current

I think that one of the fields is returning a null.  I've had similar
problems recently.

On Sep 7, 3:27=A0pm, timmg <tmillsgronin...@gmail.com> wrote:
> On Sep 7, 3:06=A0pm, Roger <lesperan...@natpro.com> wrote:
>
>
>
>
>
> > On Sep 7, 8:14=A0am, "James A. Fortune" <CDMAPos...@FortuneJames.com>
> > wrote:
>
> > > On Sep 3, 7:36=A0am, Roger <lesperan...@natpro.com> wrote:
>
> > > > I've got a form based on a sql server table, the recordsource is
> > > > =A0 =A0select * from table where id =3D foo
>
> > > > the form has textboxes, combo boxes - nothing special
>
> > > > I periodically get error
> > > > =A0 =A0Operation is not supported for this type of object. ,DAO.Fie=
lds ,
> > > > 3251
>
> > > > when clicking a command button that does
> > > > =A0 =A0 if me.dirty then
> > > > =A0 =A0 =A0 =A0 =A0me.dirty =3D false
> > > > =A0 =A0 endif
>
> > > > the beforeUpdate event just checks that certain fields are filled i=
n,
> > > > popping up a message and setting cancel=3Dtrue
>
> > > > this was not occurring with access97, does anyone have an idea as t=
o
> > > > why this is happening ?
>
> > > This is a shot in the dark. =A0Did you turn off Name AutoCorrect and
> > > apply any available Service Packs? =A0That guess is based on an old K=
B
> > > article and its advice:
>
> > >http://support.microsoft.com/kb/247488
>
> > > James A. Fortune
> > > CDMAPos...@FortuneJames.com- Hide quoted text -
>
> > > - Show quoted text -
>
> > I checked both, and yes,
> > =A0 =A0name autocorrect is off
> > =A0 =A0service pack is current
>
> I think that one of the fields is returning a null. =A0I've had similar
> problems recently.- Hide quoted text -
>
> - Show quoted text -

I don't understand, isn't reading / writing a null field within a form
valid ?

since this happens with 'me.dirty =3D false', have you found a condition
where writing a null field causes a problem

On Sep 7, 4:06=A0pm, Roger <lesperan...@natpro.com> wrote:
> On Sep 7, 8:14=A0am, "James A. Fortune" <CDMAPos...@FortuneJames.com>
> wrote:
>
>
>
> > On Sep 3, 7:36=A0am, Roger <lesperan...@natpro.com> wrote:
>
> > > I've got a form based on a sql server table, the recordsource is
> > > =A0 =A0select * from table where id =3D foo
>
> > > the form has textboxes, combo boxes - nothing special
>
> > > I periodically get error
> > > =A0 =A0Operation is not supported for this type of object. ,DAO.Field=
s ,
> > > 3251
>
> > > when clicking a command button that does
> > > =A0 =A0 if me.dirty then
> > > =A0 =A0 =A0 =A0 =A0me.dirty =3D false
> > > =A0 =A0 endif
>
> > > the beforeUpdate event just checks that certain fields are filled in,
> > > popping up a message and setting cancel=3Dtrue
>
> > > this was not occurring with access97, does anyone have an idea as to
> > > why this is happening ?
>
> > This is a shot in the dark. =A0Did you turn off Name AutoCorrect and
> > apply any available Service Packs? =A0That guess is based on an old KB
> > article and its advice:
>
> >http://support.microsoft.com/kb/247488
>
> > James A. Fortune
> > CDMAPos...@FortuneJames.com- Hide quoted text -
>
> > - Show quoted text -
>
> I checked both, and yes,
> =A0 =A0name autocorrect is off
> =A0 =A0service pack is current

The thread:

http://groups.google.com/group/microsoft.public.access.formscoding/browse_f=
rm/thread/c9d2e1ce344c9365

might give you some ideas.

What happens if you use a copy of your table and take the SQL Server
timestamp field out?

James. A. Fortune
CDMAPoster@FortuneJames.com