|
|
I have an 2003 access database that works fine on Windows XP, but errors out
on the docmd.openform line of code (OpenForm action was cancelled) after
upgrading to Vista. Strangely enough, this is only a problem for one form, so
far. All the other forms that have the same code work fine. Basically, I have
the user select a record from a subform and then click on a button (which
rebuilds the query for another form, saves it, and then opens the form to
allow editing of the selected record). Thanks for your help.
|
|
1. Does the docmd.openform include an openarg?
2. And does it refers to a control on a form?
3. Or the openning form refers to a control with a value?
You'll most likely need to compile,compact and repair your database in
Windows Vista than redeploy. It should work, if it does not than, do a little
change in your code.
Crossh wrote:
[Quoted Text] >I have an 2003 access database that works fine on Windows XP, but errors out
>on the docmd.openform line of code (OpenForm action was cancelled) after
>upgrading to Vista. Strangely enough, this is only a problem for one form, so
>far. All the other forms that have the same code work fine. Basically, I have
>the user select a record from a subform and then click on a button (which
>rebuilds the query for another form, saves it, and then opens the form to
>allow editing of the selected record). Thanks for your help.
--
Please Rate the posting if helps you
Message posted via http://www.accessmonster.com
|
|
1. Yes it includes OpenArgs
DoCmd.OpenForm "frmNameOfForm", , , , , , "Edit"
2. No, it does not refer to a control on a form. It's used in the logic of
the processing.
3. The opening form refers to me.OpenArgs which in this case is "Edit".
The strange thing is that I have an almost identical set of forms, using the
same logic, and they work fine. Re-compiling in Vista everytime would not
work, only one of my users has it (not me), and this database gets
re-distributed with changes almost daily.
I always compact & repair before distributing
"AccessVandal via AccessMonster.com" wrote:
[Quoted Text] > 1. Does the docmd.openform include an openarg? > 2. And does it refers to a control on a form? > 3. Or the openning form refers to a control with a value? > > You'll most likely need to compile,compact and repair your database in > Windows Vista than redeploy. It should work, if it does not than, do a little > change in your code. > > Crossh wrote: > >I have an 2003 access database that works fine on Windows XP, but errors out > >on the docmd.openform line of code (OpenForm action was cancelled) after > >upgrading to Vista. Strangely enough, this is only a problem for one form, so > >far. All the other forms that have the same code work fine. Basically, I have > >the user select a record from a subform and then click on a button (which > >rebuilds the query for another form, saves it, and then opens the form to > >allow editing of the selected record). Thanks for your help. > > -- > Please Rate the posting if helps you > > Message posted via http://www.accessmonster.com> > |
|
I'm clueless about this error Vista, it is strange as it does not happen in
XP. What I did was to simply modify my code in XP or Vista than can my
application work. I'm not sure a about what's in the PC environment that
might cause this problem. As I'm only aware that some of the Windows XP or
Vista updates can cause issues. I'm sure the A2K3 version is updated to SP3?
It may not work in your case but you might want to give it a try. Here's what
I would suggest.
Dim strOpenArg as String
strOpenArg = "Edit"
DoCmd.OpenForm "frmNameOfForm", , , , , , strOpenArg
Where were cases where in Vista a control value was not readable thus,
causing errors.
Crossh wrote:
[Quoted Text] >1. Yes it includes OpenArgs
>DoCmd.OpenForm "frmNameOfForm", , , , , , "Edit"
>2. No, it does not refer to a control on a form. It's used in the logic of
>the processing.
>3. The opening form refers to me.OpenArgs which in this case is "Edit".
>
>The strange thing is that I have an almost identical set of forms, using the
>same logic, and they work fine. Re-compiling in Vista everytime would not
>work, only one of my users has it (not me), and this database gets
>re-distributed with changes almost daily.
>I always compact & repair before distributing
>
>> 1. Does the docmd.openform include an openarg?
>> 2. And does it refers to a control on a form?
>[quoted text clipped - 11 lines]
>> >rebuilds the query for another form, saves it, and then opens the form to
>> >allow editing of the selected record). Thanks for your help.
--
Please Rate the posting if helps you
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/200812/1
|
|
I just discovered something using the Vista OS, when I go into any ODBC
linked (SQL 2005) table and try to filter any date (just by clicking on the
Filter By Selection button) I get the error message, "Microsoft Access has
stopped working" and it closes the db down. Apparently Vista cannot filter
the date, which happens to be in the query that opens the form.
"AccessVandal via AccessMonster.com" wrote:
[Quoted Text] > I'm clueless about this error Vista, it is strange as it does not happen in
> XP. What I did was to simply modify my code in XP or Vista than can my
> application work. I'm not sure a about what's in the PC environment that
> might cause this problem. As I'm only aware that some of the Windows XP or
> Vista updates can cause issues. I'm sure the A2K3 version is updated to SP3?
>
> It may not work in your case but you might want to give it a try. Here's what
> I would suggest.
>
> Dim strOpenArg as String
>
> strOpenArg = "Edit"
>
> DoCmd.OpenForm "frmNameOfForm", , , , , , strOpenArg
>
> Where were cases where in Vista a control value was not readable thus,
> causing errors.
>
|
|
That's what the problem in Vista.
The date problem is very consistant. In debuging, the date was correct but
Access VBA can't read the date and will throw an error. Nothing to do with
regional settings at all, settings are in US even that did not work.
The closes windows update on XP was KB956391.
Crossh wrote:
[Quoted Text] >I just discovered something using the Vista OS, when I go into any ODBC
>linked (SQL 2005) table and try to filter any date (just by clicking on the
>Filter By Selection button) I get the error message, "Microsoft Access has
>stopped working" and it closes the db down. Apparently Vista cannot filter
>the date, which happens to be in the query that opens the form.
--
Please Rate the posting if helps you
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/200812/1
|
|
|