dbTalk Databases Forums  

access2007 - error 3251 - Operation is not supported for this type of object

comp.databases.ms-access comp.databases.ms-access


Discuss access2007 - error 3251 - Operation is not supported for this type of object in the comp.databases.ms-access forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Roger
 
Posts: n/a

Default access2007 - error 3251 - Operation is not supported for this type of object - 09-03-2010 , 06:36 AM






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 ?

Reply With Quote
  #2  
Old   
Chuck Grimsby
 
Posts: n/a

Default Re: access2007 - error 3251 - Operation is not supported for thistype of object - 09-05-2010 , 09:48 AM






On Sep 3, 6:36*am, Roger <lesperan... (AT) natpro (DOT) com> wrote:
Quote:
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 ?
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.

Reply With Quote
  #3  
Old   
Roger
 
Posts: n/a

Default Re: access2007 - error 3251 - Operation is not supported for thistype of object - 09-06-2010 , 08:22 AM



On Sep 5, 8:48*am, Chuck Grimsby <cgat... (AT) gmail (DOT) com> wrote:
Quote:
On Sep 3, 6:36*am, Roger <lesperan... (AT) natpro (DOT) com> wrote:





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 ?

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.- Hide quoted text -

- Show quoted text -
I checked, no missing references
using only DAO

Reply With Quote
  #4  
Old   
James A. Fortune
 
Posts: n/a

Default Re: access2007 - error 3251 - Operation is not supported for thistype of object - 09-07-2010 , 09:14 AM



On Sep 3, 7:36*am, Roger <lesperan... (AT) natpro (DOT) com> wrote:
Quote:
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 ?
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 (AT) FortuneJames (DOT) com

Reply With Quote
  #5  
Old   
Roger
 
Posts: n/a

Default Re: access2007 - error 3251 - Operation is not supported for thistype of object - 09-07-2010 , 03:06 PM



On Sep 7, 8:14*am, "James A. Fortune" <CDMAPos... (AT) FortuneJames (DOT) com>
wrote:
Quote:
On Sep 3, 7:36*am, Roger <lesperan... (AT) natpro (DOT) com> wrote:





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 ?

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
CDMAPos... (AT) FortuneJames (DOT) com- Hide quoted text -

- Show quoted text -
I checked both, and yes,
name autocorrect is off
service pack is current

Reply With Quote
  #6  
Old   
timmg
 
Posts: n/a

Default Re: access2007 - error 3251 - Operation is not supported for thistype of object - 09-07-2010 , 04:27 PM



On Sep 7, 3:06*pm, Roger <lesperan... (AT) natpro (DOT) com> wrote:
Quote:
On Sep 7, 8:14*am, "James A. Fortune" <CDMAPos... (AT) FortuneJames (DOT) com
wrote:





On Sep 3, 7:36*am, Roger <lesperan... (AT) natpro (DOT) com> wrote:

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 ?

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
CDMAPos... (AT) FortuneJames (DOT) com- Hide quoted text -

- Show quoted text -

I checked both, and yes,
* *name autocorrect is off
* *service pack is current
I think that one of the fields is returning a null. I've had similar
problems recently.

Reply With Quote
  #7  
Old   
Roger
 
Posts: n/a

Default Re: access2007 - error 3251 - Operation is not supported for thistype of object - 09-08-2010 , 05:32 AM



On Sep 7, 3:27*pm, timmg <tmillsgronin... (AT) gmail (DOT) com> wrote:
Quote:
On Sep 7, 3:06*pm, Roger <lesperan... (AT) natpro (DOT) com> wrote:





On Sep 7, 8:14*am, "James A. Fortune" <CDMAPos... (AT) FortuneJames (DOT) com
wrote:

On Sep 3, 7:36*am, Roger <lesperan... (AT) natpro (DOT) com> wrote:

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 ?

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
CDMAPos... (AT) FortuneJames (DOT) com- Hide quoted text -

- Show quoted text -

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

I think that one of the fields is returning a null. *I'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 = false', have you found a condition
where writing a null field causes a problem

Reply With Quote
  #8  
Old   
James A. Fortune
 
Posts: n/a

Default Re: access2007 - error 3251 - Operation is not supported for thistype of object - 09-08-2010 , 09:14 AM



On Sep 7, 4:06*pm, Roger <lesperan... (AT) natpro (DOT) com> wrote:
Quote:
On Sep 7, 8:14*am, "James A. Fortune" <CDMAPos... (AT) FortuneJames (DOT) com
wrote:



On Sep 3, 7:36*am, Roger <lesperan... (AT) natpro (DOT) com> wrote:

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 ?

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
CDMAPos... (AT) FortuneJames (DOT) com- Hide quoted text -

- Show quoted text -

I checked both, and yes,
* *name autocorrect is off
* *service pack is current
The thread:

http://groups.google.com/group/micro...d2e1ce344c9365

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 (AT) FortuneJames (DOT) com

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.