A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Using Forms
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Funky Save Record Stuff



 
 
Thread Tools Display Modes
  #1  
Old April 14th, 2008, 04:34 PM posted to comp.databases.ms-access,microsoft.public.access,microsoft.public.access.forms
Neil
external usenet poster
 
Posts: 311
Default Funky Save Record Stuff

Was working in A2003 and noticed that the Save Record item on the Records
menu was not available when the record was not dirty. In A2000, Save Record
was always available. (This is a problem for me because I have Docmd.Runcmd
acCmdSaveRecord code all over the place, which never gave an error before.
But now it was giving an error when the Save Record menu command wasn't
available.)

So I went back to A2000 and confirmed that the Save Record menu command is
always available, whether the record is dirty or not. So I concluded this
was a change in A2003, that the menu item's only available when the record's
actually dirty.

However...... when I went back to A2003 and tested it again, I noticed that
it was acting in the same way as A2000, with the Save Record menu item
always available!

So, in summary:

In A2003, Save Record menu item was only available when record was actually
dirty (causing an error when docmd.runcmd accmdsaverecord was run when the
record was not dirty).

Went to A2000 and confirmed that the menu item was always available, whether
the record was dirty or not.

And when I returned to A2003, all of a sudden the menu item was always
available, as it is in A2000, though a few minutes before it had only been
available when the record was dirty!

So I was wondering if anyone else has noticed these shenanigans from A2003,
or has any idea what's going on, and why the funcationality would change
like that. Also, how does A2003 act in your copy: is the Save Record menu
item always available; or is it grayed out when the record's not dirty?

Thanks!

Neil


  #2  
Old April 14th, 2008, 05:57 PM posted to comp.databases.ms-access,microsoft.public.access,microsoft.public.access.forms
Lisa Moody
external usenet poster
 
Posts: 16
Default Funky Save Record Stuff

Neil,

Do you see this in SP3 and not in SP2 when using MS Access 2003? I have
another situation previously posted about a problem with SP3 and my
developer is having trouble with Save Record when it's a memo field and
there is nothing in it. I am going to post that information in my previous
post, but it might be the same thing. It only happens when connecting via
ODBC to an SQL db and not when Access is the backend.

Lisa



"Neil" wrote in message
...
Was working in A2003 and noticed that the Save Record item on the Records
menu was not available when the record was not dirty. In A2000, Save
Record was always available. (This is a problem for me because I have
Docmd.Runcmd acCmdSaveRecord code all over the place, which never gave an
error before. But now it was giving an error when the Save Record menu
command wasn't available.)

So I went back to A2000 and confirmed that the Save Record menu command is
always available, whether the record is dirty or not. So I concluded this
was a change in A2003, that the menu item's only available when the
record's actually dirty.

However...... when I went back to A2003 and tested it again, I noticed
that it was acting in the same way as A2000, with the Save Record menu
item always available!

So, in summary:

In A2003, Save Record menu item was only available when record was
actually dirty (causing an error when docmd.runcmd accmdsaverecord was run
when the record was not dirty).

Went to A2000 and confirmed that the menu item was always available,
whether the record was dirty or not.

And when I returned to A2003, all of a sudden the menu item was always
available, as it is in A2000, though a few minutes before it had only been
available when the record was dirty!

So I was wondering if anyone else has noticed these shenanigans from
A2003, or has any idea what's going on, and why the funcationality would
change like that. Also, how does A2003 act in your copy: is the Save
Record menu item always available; or is it grayed out when the record's
not dirty?

Thanks!

Neil



  #3  
Old April 14th, 2008, 07:23 PM posted to comp.databases.ms-access,microsoft.public.access,microsoft.public.access.forms
Lisa Moody
external usenet poster
 
Posts: 16
Default Funky Save Record Stuff

Here is what I posted in my other thread and it might apply for this also:

The problem appears to be with the way updated Access handles the empty
string (""). Specifically with Memo type fields mapped to ODBC SQL
connections of LONG VARCHAR type. In previous versions of Access, the empty
string would be passed to the SQL back end as a Null. This works great
because text boxes don't accept Null as a value, so if the text box was
empty, the empty string could be passed via a RunSQL command just like any
other string and it would be translated to Null in the back end data source.
Now, we have to add exception handling for zero length strings. This is
probably a side effect of a fix or could have been determined to be a
security hole. Either way it's causing rework and I didn't find any
documentation for the change.

The catch is that having the code add a space to the field doesn't make it
dirty "enough?" and doesn't solve our immediate need.

Lisa
"Lisa Moody" wrote in message
. ..
Neil,

Do you see this in SP3 and not in SP2 when using MS Access 2003? I have
another situation previously posted about a problem with SP3 and my
developer is having trouble with Save Record when it's a memo field and
there is nothing in it. I am going to post that information in my
previous post, but it might be the same thing. It only happens when
connecting via ODBC to an SQL db and not when Access is the backend.

Lisa



"Neil" wrote in message
...
Was working in A2003 and noticed that the Save Record item on the Records
menu was not available when the record was not dirty. In A2000, Save
Record was always available. (This is a problem for me because I have
Docmd.Runcmd acCmdSaveRecord code all over the place, which never gave an
error before. But now it was giving an error when the Save Record menu
command wasn't available.)

So I went back to A2000 and confirmed that the Save Record menu command
is always available, whether the record is dirty or not. So I concluded
this was a change in A2003, that the menu item's only available when the
record's actually dirty.

However...... when I went back to A2003 and tested it again, I noticed
that it was acting in the same way as A2000, with the Save Record menu
item always available!

So, in summary:

In A2003, Save Record menu item was only available when record was
actually dirty (causing an error when docmd.runcmd accmdsaverecord was
run when the record was not dirty).

Went to A2000 and confirmed that the menu item was always available,
whether the record was dirty or not.

And when I returned to A2003, all of a sudden the menu item was always
available, as it is in A2000, though a few minutes before it had only
been available when the record was dirty!

So I was wondering if anyone else has noticed these shenanigans from
A2003, or has any idea what's going on, and why the funcationality would
change like that. Also, how does A2003 act in your copy: is the Save
Record menu item always available; or is it grayed out when the record's
not dirty?

Thanks!

Neil





  #4  
Old April 15th, 2008, 05:58 AM posted to comp.databases.ms-access,microsoft.public.access,microsoft.public.access.forms
Neil
external usenet poster
 
Posts: 311
Default Funky Save Record Stuff

I am using SP3, so I don't know about SP2. And, yes, mine is a SQL Server
backend (via ODBC) as well. Whatever happened (with Save Record not being
available in a non-dirty record), it cleared itself after going to A2000 and
then back to A2003 again. But the version of Access I'm using was the same
in both cases.



"Lisa Moody" wrote in message
. ..
Neil,

Do you see this in SP3 and not in SP2 when using MS Access 2003? I have
another situation previously posted about a problem with SP3 and my
developer is having trouble with Save Record when it's a memo field and
there is nothing in it. I am going to post that information in my
previous post, but it might be the same thing. It only happens when
connecting via ODBC to an SQL db and not when Access is the backend.

Lisa



"Neil" wrote in message
...
Was working in A2003 and noticed that the Save Record item on the Records
menu was not available when the record was not dirty. In A2000, Save
Record was always available. (This is a problem for me because I have
Docmd.Runcmd acCmdSaveRecord code all over the place, which never gave an
error before. But now it was giving an error when the Save Record menu
command wasn't available.)

So I went back to A2000 and confirmed that the Save Record menu command
is always available, whether the record is dirty or not. So I concluded
this was a change in A2003, that the menu item's only available when the
record's actually dirty.

However...... when I went back to A2003 and tested it again, I noticed
that it was acting in the same way as A2000, with the Save Record menu
item always available!

So, in summary:

In A2003, Save Record menu item was only available when record was
actually dirty (causing an error when docmd.runcmd accmdsaverecord was
run when the record was not dirty).

Went to A2000 and confirmed that the menu item was always available,
whether the record was dirty or not.

And when I returned to A2003, all of a sudden the menu item was always
available, as it is in A2000, though a few minutes before it had only
been available when the record was dirty!

So I was wondering if anyone else has noticed these shenanigans from
A2003, or has any idea what's going on, and why the funcationality would
change like that. Also, how does A2003 act in your copy: is the Save
Record menu item always available; or is it grayed out when the record's
not dirty?

Thanks!

Neil





  #5  
Old April 15th, 2008, 06:05 AM posted to comp.databases.ms-access,microsoft.public.access,microsoft.public.access.forms
Neil
external usenet poster
 
Posts: 311
Default Funky Save Record Stuff

Lisa,

I'm not experiencing this problem. But, first, I never heard of Long
Varchar. I've heard of varchar and nvarchar. Are you referring to nvarchar?

Second, I'm not following what your problem is. You're trying to store an
empty string in a memo field and it's not getting converted to Null? Maybe
you can elaborate.


"Lisa Moody" wrote in message
...
Here is what I posted in my other thread and it might apply for this also:

The problem appears to be with the way updated Access handles the empty
string (""). Specifically with Memo type fields mapped to ODBC SQL
connections of LONG VARCHAR type. In previous versions of Access, the
empty string would be passed to the SQL back end as a Null. This works
great because text boxes don't accept Null as a value, so if the text box
was empty, the empty string could be passed via a RunSQL command just like
any other string and it would be translated to Null in the back end data
source. Now, we have to add exception handling for zero length strings.
This is probably a side effect of a fix or could have been determined to
be a security hole. Either way it's causing rework and I didn't find any
documentation for the change.

The catch is that having the code add a space to the field doesn't make it
dirty "enough?" and doesn't solve our immediate need.

Lisa
"Lisa Moody" wrote in message
. ..
Neil,

Do you see this in SP3 and not in SP2 when using MS Access 2003? I have
another situation previously posted about a problem with SP3 and my
developer is having trouble with Save Record when it's a memo field and
there is nothing in it. I am going to post that information in my
previous post, but it might be the same thing. It only happens when
connecting via ODBC to an SQL db and not when Access is the backend.

Lisa



"Neil" wrote in message
...
Was working in A2003 and noticed that the Save Record item on the
Records menu was not available when the record was not dirty. In A2000,
Save Record was always available. (This is a problem for me because I
have Docmd.Runcmd acCmdSaveRecord code all over the place, which never
gave an error before. But now it was giving an error when the Save
Record menu command wasn't available.)

So I went back to A2000 and confirmed that the Save Record menu command
is always available, whether the record is dirty or not. So I concluded
this was a change in A2003, that the menu item's only available when the
record's actually dirty.

However...... when I went back to A2003 and tested it again, I noticed
that it was acting in the same way as A2000, with the Save Record menu
item always available!

So, in summary:

In A2003, Save Record menu item was only available when record was
actually dirty (causing an error when docmd.runcmd accmdsaverecord was
run when the record was not dirty).

Went to A2000 and confirmed that the menu item was always available,
whether the record was dirty or not.

And when I returned to A2003, all of a sudden the menu item was always
available, as it is in A2000, though a few minutes before it had only
been available when the record was dirty!

So I was wondering if anyone else has noticed these shenanigans from
A2003, or has any idea what's going on, and why the funcationality would
change like that. Also, how does A2003 act in your copy: is the Save
Record menu item always available; or is it grayed out when the record's
not dirty?

Thanks!

Neil







 




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 Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 10:38 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.