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 » General Discussion
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Are there known issues with Vista and Acc2003



 
 
Thread Tools Display Modes
  #1  
Old February 26th, 2007, 09:07 PM posted to comp.databases.ms-access,microsoft.public.access
Tony Ciconte
external usenet poster
 
Posts: 6
Default Are there known issues with Vista and Acc2003

I have a rather complex commercial Acc2003 application (tab controls,
50K+ lines of VBA code, etc.) that will not run well at all on Windows
Vista Ultimate. I have seen posts indicating that Acc2003 MDBs should
work on Vista. However, our particular file has too many problems to
be viable on a Vista platform. Even converting it to an Acc2007 accdb
file has no positive effect.

I realize that Vista is new and should be avoided like the plague, but
we have few choices if some of our clients go to Vista.

We have been all over the MS knowledgebase and these groups without
much luck. Are there any lists of known issues and or suggestions
gathered during Vista beta that are available and if so, where?

Any and all help is greatly appreciated….

  #2  
Old February 26th, 2007, 09:18 PM posted to comp.databases.ms-access,microsoft.public.access
Di Cook
external usenet poster
 
Posts: 17
Default Are there known issues with Vista and Acc2003

Tony

Sendkeys is not supported in Acc2003 programs running under Vista.

If you also set up shortcuts that performed a compact of the database you
will have to change the shortcut to "Run as administrator" or that wont work
as well.

Regards
Di
"Tony Ciconte" wrote in message
...
I have a rather complex commercial Acc2003 application (tab controls,
50K+ lines of VBA code, etc.) that will not run well at all on Windows
Vista Ultimate. I have seen posts indicating that Acc2003 MDBs should
work on Vista. However, our particular file has too many problems to
be viable on a Vista platform. Even converting it to an Acc2007 accdb
file has no positive effect.

I realize that Vista is new and should be avoided like the plague, but
we have few choices if some of our clients go to Vista.

We have been all over the MS knowledgebase and these groups without
much luck. Are there any lists of known issues and or suggestions
gathered during Vista beta that are available and if so, where?

Any and all help is greatly appreciated..



  #3  
Old February 27th, 2007, 01:11 AM posted to comp.databases.ms-access,microsoft.public.access
Tony Toews [MVP]
external usenet poster
 
Posts: 3,776
Default Are there known issues with Vista and Acc2003

Tony Ciconte wrote:

I have a rather complex commercial Acc2003 application (tab controls,
50K+ lines of VBA code, etc.) that will not run well at all on Windows
Vista Ultimate.


What specific problems are you having?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
  #4  
Old February 27th, 2007, 09:42 AM posted to comp.databases.ms-access,microsoft.public.access
onedaywhen
external usenet poster
 
Posts: 124
Default Are there known issues with Vista and Acc2003

On Feb 27, 2:42 am, "Larry Linson" wrote:
I find it comical that anyone would recommend conversion to a
technology no longer recommended by the Access development and support team
at Microsoft


What about, for example, back in 2000 when the "Access development and
support team at Microsoft" were saying things such as, "In previous
versions of Access, Data Access Objects (DAO) was the primary data
access method. That has now changed. Although DAO is still supported,
the new way to access data is with ADO." (http://msdn2.microsoft.com/
en-us/library/aa140015(office.10).aspx)? My impression is that you
took the "no longer recommended" path and stuck with DAO, even for new
projects. Isn't it reasonable for someone to take the same approach
now with ADP, ADO, etc?

Jamie.

--


  #5  
Old February 27th, 2007, 08:01 PM posted to comp.databases.ms-access,microsoft.public.access
David W. Fenton
external usenet poster
 
Posts: 3,373
Default Are there known issues with Vista and Acc2003

"Di Cook" wrote in
:

Sendkeys is not supported in Acc2003 programs running under Vista.


No serious programmer ever uses SendKeys.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
  #6  
Old February 27th, 2007, 09:01 PM posted to comp.databases.ms-access,microsoft.public.access
Larry Linson
external usenet poster
 
Posts: 3,112
Default Are there known issues with Vista and Acc2003

"onedaywhen" wrote

Isn't it reasonable for someone to take the
same approach now with ADP, ADO, etc?


Trying to pick a fight, again, Jamie? I thought we were going to try to
avoid that... oh, well, my misunderstanding -- I suppose it was just I who
was going to try to avoid it. Hmm, I never thought you were the one posting
as "aaron", either, but maybe that, too, was my misunderstanding.

So, here's the answer to your question: "Not if that person is knowlegeable
about Access and database in general, and has evaluated both approaches, as
many of us had done in the Access 2000 timeframe."

Larry Linson
Microsoft Access MVP





  #7  
Old February 27th, 2007, 10:53 PM posted to comp.databases.ms-access,microsoft.public.access
Tim Marshall
external usenet poster
 
Posts: 17
Default Are there known issues with Vista and Acc2003

onedaywhen wrote:

What about, for example, back in 2000 when the "Access development and
support team at Microsoft" were saying things such as, "In previous
versions of Access, Data Access Objects (DAO) was the primary data
access method. That has now changed. Although DAO is still supported,
the new way to access data is with ADO." (http://msdn2.microsoft.com/
en-us/library/aa140015(office.10).aspx)


Try calling MS support now. They recommend DAO with jet. As of 2005,
when I started using A2003, anyway.

50K lines of code is easy to come up with. Do you know what a
computerized maintenance mangement system is that controls work
assignment, inventory, purchasing, maintenance and PM schedules,
workers' hours, contractors, equipment, asset, building, room, vehicle
and hundreds of other lists of things facilities managers look after?
50K is nothing.

Some of us write and maintain very large applications. There are, of
course, simpler apps that are also very important such as document
management systems. However, since about the early 90s, computer power
has been such that organizations rightly need to consolidate various
stand alone systems as much as possible so that both operational and
Decision Support information is more easily and quickly accessible.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Be Careful, Big Bird!" - Ditto "TIM-MAY!!" - Me
  #8  
Old February 28th, 2007, 12:20 AM posted to comp.databases.ms-access,microsoft.public.access
David W. Fenton
external usenet poster
 
Posts: 3,373
Default Are there known issues with Vista and Acc2003

"onedaywhen" wrote in
ups.com:

What about, for example, back in 2000 when the "Access development
and support team at Microsoft" were saying things such as, "In
previous versions of Access, Data Access Objects (DAO) was the
primary data access method. That has now changed. Although DAO is
still supported, the new way to access data is with ADO."
(http://msdn2.microsoft.com/
en-us/library/aa140015(office.10).aspx)? My impression is that you
took the "no longer recommended" path and stuck with DAO, even for
new projects. Isn't it reasonable for someone to take the same
approach now with ADP, ADO, etc?


No, it is not.

HTH.

(think about the difference between a native technology and a
translation layer)

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
  #9  
Old February 28th, 2007, 09:45 AM posted to comp.databases.ms-access,microsoft.public.access
onedaywhen
external usenet poster
 
Posts: 124
Default Are there known issues with Vista and Acc2003

On Feb 27, 8:01 pm, "Larry Linson" wrote:
I find it comical that anyone would recommend conversion to a
technology no longer recommended by the Access development and support team
at Microsoft

later

[but] Not if that person is knowlegeable
about Access and database in general, and has evaluated both approaches


OK, we now seem to be in agreement that blindly following the advice
of 'Microsoft support' is not the correct approach. I got the
impression from your early comment that you thought there was there
was direct causation between "going against the advice of Microsoft
support" and "deserving ridicule". That's why I stepped in (to break
up a fight, not to start one) and you clarified the point, for which I
thank you.

Jamie.

--


  #10  
Old February 28th, 2007, 09:47 AM posted to comp.databases.ms-access,microsoft.public.access
onedaywhen
external usenet poster
 
Posts: 124
Default Are there known issues with Vista and Acc2003

On Feb 27, 11:20 pm, "David W. Fenton"
wrote:
What about, for example, back in 2000 when the "Access development
and support team at Microsoft" were saying things such as, "In
previous versions of Access, Data Access Objects (DAO) was the
primary data access method. That has now changed. Although DAO is
still supported, the new way to access data is with ADO."
(http://msdn2.microsoft.com/
en-us/library/aa140015(office.10).aspx)? My impression is that you
took the "no longer recommended" path and stuck with DAO, even for
new projects. Isn't it reasonable for someone to take the same
approach now with ADP, ADO, etc?


No, it is not.


Because...?

Jamie.

--


 




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 12:29 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.