By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,122 Members | 906 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,122 IT Pros & Developers. It's quick & easy.

Access and Newer Development Platforms

P: n/a
Have you installed and used a new development platform such as Visual
Studio.Net on your Access development machine(s)?

Were there problems?

Were you able to maintain and revise your old
MDPs?
ADPs?
Connections to Server DBs?

What about
HTAs
WSFs
and old "classic"? ASP-HTML applications?

Did your OLEDB-ADO code need revision?

Did applications revised in the post VS.Net days continue to run on client
machines?

What about development in progress when you acquired the new technology.
Did you convert them?

Do you have any advice or comments about such a process (moving to VS.Net
or other new technology)?
--
Lyle
--
use iso date format: yyyy-mm-dd
http://www.w3.org/QA/Tips/iso-date
--
The e-mail address isn't, but you could use it to find one.
Nov 13 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Lyle Fairfield wrote:
Have you installed and used a new development platform such as Visual
Studio.Net on your Access development machine(s)?
Yes
Were there problems?
No
Were you able to maintain and revise your old
MDPs?
ADPs?
Connections to Server DBs?
Yes
What about
HTAs
WSFs
and old "classic"? ASP-HTML applications?
Still use VS6.0 for ASP, no problems apart from VS.NET registering
itself to open .sln files, just opened whichever environment and used
the MRU list or "open" to open a project.
Did your OLEDB-ADO code need revision?
In the older environments? No.
Did applications revised in the post VS.Net days continue to run on client
machines?
Yes.
What about development in progress when you acquired the new technology.
Did you convert them?
No. I'm not paid enough to do that.
Do you have any advice or comments about such a process (moving to VS.Net
or other new technology)?


I've not experienced or heard of any issues with this, the older
platforms continue to work OK. No problems in VS6, VB6 or Access (2002).

Nov 13 '05 #2

P: n/a
Trevor Best <nospam@localhost> wrote in
news:41***********************@auth.uk.news.easyne t.net:
Lyle Fairfield wrote:
Have you installed and used a new development platform such as Visual
Studio.Net on your Access development machine(s)?


Yes
Were there problems?


No
Were you able to maintain and revise your old
MDPs?
ADPs?
Connections to Server DBs?


Yes
What about
HTAs
WSFs
and old "classic"? ASP-HTML applications?


Still use VS6.0 for ASP, no problems apart from VS.NET registering
itself to open .sln files, just opened whichever environment and used
the MRU list or "open" to open a project.
Did your OLEDB-ADO code need revision?


In the older environments? No.
Did applications revised in the post VS.Net days continue to run on
client machines?


Yes.
What about development in progress when you acquired the new
technology. Did you convert them?


No. I'm not paid enough to do that.
Do you have any advice or comments about such a process (moving to
VS.Net or other new technology)?


I've not experienced or heard of any issues with this, the older
platforms continue to work OK. No problems in VS6, VB6 or Access (2002).


Thanks, Trevor, ... sounds like a piece of cake! :-)

--
Lyle
--
use iso date format: yyyy-mm-dd
http://www.w3.org/QA/Tips/iso-date
--
The e-mail address isn't, but you could use it to find one.
Nov 13 '05 #3

P: n/a
On 16 Aug 2004 10:22:25 GMT, Lyle Fairfield <Lo******@FFDBA.Com>
wrote:

I run them side by side and I'm not experiencing any problems, other
than sometimes running out of GDI memory.
Never did HTAs or WSFs - can't comment on that.
I would never convert a project already under development. Unless the
client badly wanted it.

I'm somewhat opposed to porting apps to .NET, because it's such a
different environment. Rather I would want to re-implement using the
..NET preferred approach. One such nice approach is the .NET Starter
Kits at ibuyspy.com, and its rebuttal at
http://msdn.microsoft.com/library/de...SKinVS2005.asp

-Tom.
Have you installed and used a new development platform such as Visual
Studio.Net on your Access development machine(s)?

Were there problems?

Were you able to maintain and revise your old
MDPs?
ADPs?
Connections to Server DBs?

What about
HTAs
WSFs
and old "classic"? ASP-HTML applications?

Did your OLEDB-ADO code need revision?

Did applications revised in the post VS.Net days continue to run on client
machines?

What about development in progress when you acquired the new technology.
Did you convert them?

Do you have any advice or comments about such a process (moving to VS.Net
or other new technology)?
--
Lyle
--
use iso date format: yyyy-mm-dd
http://www.w3.org/QA/Tips/iso-date


Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.