Access 2007 bug

[Bruno Campanini]

Somebody claims there is a bug such as:

"I attempted to change the record source in a simple form using the query
builder, selecting a table adding three fields, then click save and update
SQL statement in the record source. Once back in the form the original table
is in the record source and was not updated from the query builder. I ahve
compacted and repaired, closed the database..."

My Access 2007 works fine at this point.

Any comments?

Bruno

 

[Allen Browne]

Tell them to make sure they tab out of the RecordSource property in the
Properties sheet after changing the SQL statement, before they try to save
the changes.

 

[Bruno Campanini]

Tell them to make sure they tab out of the RecordSource property in the
Properties sheet after changing the SQL statement, before they try to save
the changes.

I presume they do so, otherwise that would be a bug for
all Access versions!

Bruno

 

[Dirk Goldgar]

I presume they do so, otherwise that would be a bug for
all Access versions!

No, there's definitely a new behavior involved, because I've encountered
this several times while working with A2007, when I never did with previous
versions. I hadn't figured out exactly what was the cause of the problem;
I just noted that my change to property didn't get saved. Allen's post may
well be the answer. I'll have to test it.

 

[giorgio rancati]

No, there's definitely a new behavior involved, because I've encountered
this several times while working with A2007, when I never did with
previous versions. I hadn't figured out exactly what was the cause of the
problem; I just noted that my change to property didn't get saved.
Allen's post may well be the answer. I'll have to test it.

Hi Dirk,

try these steps to reproduce the behaviour

1: Open a form with one table and some fields in recordsource
2: Modify the recordsourse with query builder and remove one field
3: Close the property windows
4: Close the query builder and say yes to save changes
5: Close the form, you can see that Access doesn't prompt to save changes.
6: Reopen the form and see if it actually saved the changes

bye.

 

[Jerry Whittle]

I just ran into this behavior last night. I saved and closed the form. After
reopening the form, the new SQL started working.

I may also have moved around the property sheet as Allen suggested, but
don't remember doing so.

Definitely different than all the other versions of Access back to V1.0.

 

[Bruno Campanini]

Hi Dirk,

try these steps to reproduce the behaviour

1: Open a form with one table and some fields in recordsource
2: Modify the recordsourse with query builder and remove one field
3: Close the property windows
4: Close the query builder and say yes to save changes
5: Close the form, you can see that Access doesn't prompt to save changes.
6: Reopen the form and see if it actually saved the changes

The new behavior is probably only that:
- with Access 2003 you are not allowed to close Property
Sheet before Query Builder as the PSheet disappears
as soon as you open QBuilder.
- with Access 2007 PSheet doesn't disappear and you
can close it before QBuilder.

But, how can you think QBuilder can update PSheet
immediately, as you type in?
It seems to me no database object can NORMALLY
update while you are typing; you must leave it before!

BTW, tabbing out of the RecordSource field does the
job without problems.
That's such a usual procedure to me that I spent some
time in reproducing the behavior you mentioned!

Ciao
Bruno

 

[BruceM]

The new behavior is probably only that:
- with Access 2003 you are not allowed to close Property
Sheet before Query Builder as the PSheet disappears
as soon as you open QBuilder.
- with Access 2007 PSheet doesn't disappear and you
can close it before QBuilder.

But, how can you think QBuilder can update PSheet
immediately, as you type in?
It seems to me no database object can NORMALLY
update while you are typing; you must leave it before!

BTW, tabbing out of the RecordSource field does the
job without problems.
That's such a usual procedure to me that I spent some
time in reproducing the behavior you mentioned!

Ciao
Bruno

I have never noticed that it is necessary to leave an object before it
updates. I can modify the Record Source in Design View, then switch to Form
View and see the result of the changes without ever saving the form. The
point, I think, is that it is necessary to tab (or click, I suppose) out of
the Record Source property before saving the form. I agree that it
shouldn't be necessary, but it seems to be the case.

 

[Bruno Campanini]

I have never noticed that it is necessary to leave an object before it
updates. I can modify the Record Source in Design View, then switch to
Form View and see the result of the changes without ever saving the form.
The point, I think, is that it is necessary to tab (or click, I suppose)
out of the Record Source property before saving the form. I agree that it
shouldn't be necessary, but it seems to be the case.

Do you have a field / record updated without moving
away from them?

Bruno

 

[Dirk Goldgar]

Do you have a field / record updated without moving
away from them?

Certainly you do, when you close a form with a dirty record.

 

[BruceM]

In Access 2003 and earlier I can revise a field's data, then close the form
or the database, and the changes are saved. I was replying specifically to
your contention that it is necessary to *leave an object* in order for it to
be updated. If I attempt to close an object I have changed but not saved, I
am prompted to save the changes. If I save it before closing, it closes
without ado, and all changes are saved. In any case, all changes are saved,
without any special need to tab or click anywhere new. From what I am
reading, this is not always the case with Access 2007, which means it
behaves differently in some ways than earlier versions.
Of course it is not truly possible to test whether a change has been saved
without closing and reopening, so if that is your point I will not disagree.

 

[david s.]

it's what allen said. it is a known 2007 bug (i found it on a list somewhere)
and you simply have to tab to another property before saving the change.

 

[Nicholas Meyer]

check your virus scan

it's what allen said. it is a known 2007 bug (i found it on a list
somewhere)
and you simply have to tab to another property before saving the change.