| Subject: Updating an old application |
| Group: microsoft.public.vstudio.general |
| Date: 9/17/2008 7:28:05 AM |
| From: =?Utf-8?B?Um9uRw==?= [Email Address Protection] |
Hi, I'm in the process of inheriting an application written to use Access97 and the Access97 runtime. It's a mature application with a ton of functionality, but it does need to be brought forward. My goal is to re-architect the system so that it can run on PCs, Macs, or the Web. I *think* I should be moving the system into the .Net environment, but I'm unclear as to what options I really have, short of a full re-write, which I'm not opposed to doing. I understand that the Mac will not be supported by .Net (as far as I know) but could be by using something like the mono project. I'm also not opposed to completely changing platforms, ie, Java/MySQL/PHP, but this is, after all, the Microsoft Developer's forum :-) I think what I'm shooting for is a common database layout with common logic components, but with independent front ends depending on the platform. Anyway, any thoughts you might have on this would be greatly appreciated. Also, if this question is more appropriate to another group, some direction would be appreciated on that as well. Thanks and have a good day. Ron |
| Back |
| Subject: Re: Updating an old application |
| Group: microsoft.public.vstudio.general |
| Date: 9/17/2008 8:07:29 AM |
| From: "Norman Yuan" [Email Address Protection] |
The choice is obvious: Access only runs on Windows desktop, it does not run on Mac (unless you use Wndows emulator), nor be used via the Internet. If you re-write it as .NET desktop, it is still Window only. No other OS runs .NET on user end. If you want to make it a web app, so that users with Win/Mac can access it vis web browser, then you need to throw away whatever the current Access app has and re-write the whole thing, be it .NET web app or Java or some other technologies. "RonG" <RonG@discussions.microsoft.com> wrote in message news:EA3E0B68-B92C-475F-8947-73A17DC70F80@microsoft.com... > Hi, > I'm in the process of inheriting an application written to use Access97 > and > the Access97 runtime. It's a mature application with a ton of > functionality, > but it does need to be brought forward. My goal is to re-architect the > system so that it can run on PCs, Macs, or the Web. I *think* I should be > moving the system into the .Net environment, but I'm unclear as to what > options I really have, short of a full re-write, which I'm not opposed to > doing. I understand that the Mac will not be supported by .Net (as far as > I > know) but could be by using something like the mono project. I'm also not > opposed to completely changing platforms, ie, Java/MySQL/PHP, but this is, > after all, the Microsoft Developer's forum :-) > > I think what I'm shooting for is a common database layout with common > logic > components, but with independent front ends depending on the platform. > > Anyway, any thoughts you might have on this would be greatly appreciated. > Also, if this question is more appropriate to another group, some > direction > would be appreciated on that as well. > > Thanks and have a good day. > > Ron |
| Back |
| Subject: Re: Updating an old application |
| Group: microsoft.public.vstudio.general |
| Date: 9/17/2008 8:23:38 AM |
| From: David Wilkinson [Email Address Protection] |
RonG wrote: > Hi, > I'm in the process of inheriting an application written to use Access97 and > the Access97 runtime. It's a mature application with a ton of functionality, > but it does need to be brought forward. My goal is to re-architect the > system so that it can run on PCs, Macs, or the Web. I *think* I should be > moving the system into the .Net environment, but I'm unclear as to what > options I really have, short of a full re-write, which I'm not opposed to > doing. I understand that the Mac will not be supported by .Net (as far as I > know) but could be by using something like the mono project. I'm also not > opposed to completely changing platforms, ie, Java/MySQL/PHP, but this is, > after all, the Microsoft Developer's forum :-) > > I think what I'm shooting for is a common database layout with common logic > components, but with independent front ends depending on the platform. > > Anyway, any thoughts you might have on this would be greatly appreciated. > Also, if this question is more appropriate to another group, some direction > would be appreciated on that as well. Ron: I don't know if this would work for you (or your customers), but CrossOver Mac is an inexpensive application that allows many/most Windows programs to run "natively" on Intel Mac's. CrossOver Mac (and CrossOver Linux) are based on the WINE project. -- David Wilkinson Visual C++ MVP |
| Back |
| Subject: Re: Updating an old application |
| Group: microsoft.public.vstudio.general |
| Date: 9/18/2008 6:21:46 AM |
| From: Anthony.Youngman@eca-international.com |
On Sep 17, 3:28=A0pm, RonG <R...@discussions.microsoft.com> wrote: > Hi, > I'm in the process of inheriting an application written to use Access97 a= nd > the Access97 runtime. =A0It's a mature application with a ton of function= ality, > but it does need to be brought forward. =A0My goal is to re-architect the > system so that it can run on PCs, Macs, or the Web. =A0I *think* I should= be > moving the system into the .Net environment, but I'm unclear as to what > options I really have, short of a full re-write, which I'm not opposed to > doing. =A0I understand that the Mac will not be supported by .Net (as far= as I > know) but could be by using something like the mono project. =A0I'm also = not > opposed to completely changing platforms, ie, Java/MySQL/PHP, but this is= , > after all, the Microsoft Developer's forum :-) =A0 > > I think what I'm shooting for is a common database layout with common log= ic > components, but with independent front ends depending on the platform. > > Anyway, any thoughts you might have on this would be greatly appreciated.= =A0 > Also, if this question is more appropriate to another group, some directi= on > would be appreciated on that as well. > > Thanks and have a good day. > > Ron Think of things a bit differently (I've read some of the other responses :-) Firstly, separate the front and back ends. Port the database to SQL- Server and replace all the access tables by links to SQL-Server. At the same time, duplicate that in something like MySQL. Your back end is now platform-agnostic, but everybody still has to use Access as their front end. Now rewrite the front end in something like mono or Tcl/Tk. Your front- end is now platform-agnostic ... And off you go :-) Use the right tool for the job, and don't be fooled by Access, which is actually a collection of tools for data storage, entry, manipulation and reporting. Cheers, Wol |
| Back |