Runtime etc.

  • Thread starter Thread starter google3luo359
  • Start date Start date
G

google3luo359

I have Access 2000 presently, (no developers kit).
A system that I'd like to run my app on doesn't have Access presently
on most of its computers.
The computers that don't have Access are running Windows XP
Those that have Access (2000), very few, are running Win '98.


What are my options to get this app running in this environment?
If I bought A2000 Developer's Kit, would it be easier to bring my A2000
app into the above environment?
Would AXP be a better choice, and if so, would I have any problems
porting my A2000 app?

Thanks for you tips!

Ric
 
Your biggest problem might be finding an Office 2000 Developer's Kit. Other
than making sure any ActiveX controls work in an Access 2002 environment,
you should be able to just adjust any references and convert the app. You
may also have a hard time finding a Developer's Kit for Office 2002.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access
 
Arvin Meyer said:
Your biggest problem might be finding an
Office 2000 Developer's Kit. Other
than making sure any ActiveX controls work
in an Access 2002 environment, you should
be able to just adjust any references and con-
vert the app. You may also have a hard time
finding a Developer's Kit for Office 2002.
Click to expand...

Although both Office 2000 and 2002 have been out of production for some
years and new copies of Developer Editions are not available from Microsoft,
you may be able to find them at online auction sites and "old software"
sites.

But, there is little difference between Access 2002 and Access 2003, and
Access 2003 and the Visual Studio Tools for Office 2003 System are current
Microsoft products.

Whatever version you obtain, including the current Access 2003, be certain
that you download and apply all the Service Packs and updates that apply.

Larry Linson
Microsoft Access MVP
 
Thanks Arvin and Larry!

Assuming for the moment that I will be able to find an Office 2000 Dev.
Kit
or Office 2002 Dev. Kit, I'm still not sure how I should proceed.

You guys are writing behind tons of practical experience with Dev.
Kits.
I have absolutely none.

If a Kit is purchased (now very likely), it will be the client who will
be paying for it. I do very little development (two apps in three
years!).
So I must be sure which version Kit to buy.

Again, this is where I could use your expertise.
I understand there are the following Access versions:
Access 97, 2000, 2002, 2003, 2007 (Please let me know if I'm missing
any current ones).

Again, assuming I could purchase any of the Dev. Kits for these
versions, which of the above would you recommend?

For example, if I purchased an Access 2002 Dev. Kit.
Do I just import my .mdb file, click on make .exe file, and that's it?
The file's ready to go and I just make as many copies as needed?
Will the file run on Win '98, WinXP and future Windows versions?

Which of the above Kits require WinXP to run them?

Thanks very much!

Ric
 
You cannot make an exe file in Access. There is no stand-alone. You need to
supply the runtime environment. The developer's kits give you the license to
do so. I personally prefer to distribute only them Access files and require
the client to put the full version of Office on each machine. In the end, I
think that's less expensive, because my applications generally transcend
just database usage and require Excel, Word, and sometimes Outlook and
PowerPoint. Since VBA is the common language, you can also program
applications which use MS-Project, MapPoint, and even non-Microsoft
applications like AutoCAD and IntelliCAD.

Access versions go all the way back to version 1:

http://www.accessmvp.com/Arvin/AccessOrigins.htm

and there are developer's kits going back to version 1.1. The first one I
have used was for version 2.0. If there was a best, I'd probably choose
Access 97, but that would leave out features like Conditional Formatting,
that I use all the time. Since Office 2003 requires Windows 2000 or XP, and
you have some Windows 98 machines, my first choice, if the Win 98 machines
have 256MB of memory and aren't too old, would be Access 2002. For older
machines, I'd recommend Office 97. Avoid Office 2000, except as a file
format, because of its propensity to corrupt during development.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access
 
Thanks very much for this info Arvin, it's really helpful.
I personally prefer to distribute only them Access files and require
the client to put the full version of Office on each machine. In the end, I
think that's less expensive, because my applications generally transcend
just database usage and require Excel, Word, and sometimes Outlook and
PowerPoint...
Click to expand...

In this current situation, the client (a school/Board) would have to
decide between a developer's kit or 40-50 copies of Office/Access.
Given that this would only be an Access app. I'd think the Dev. Kit /
runtime would be more cost-effective?

you have some Windows 98 machines, my first choice, if the Win 98 machines
have 256MB of memory and aren't too old, would be Access 2002. For older
machines, I'd recommend Office 97. Avoid Office 2000, except as a file
format, because of its propensity to corrupt during development.
Click to expand...

OK, good. It sounds like Access 2002 would be the best fit for this
situation.

Thanks again! Ric
 
Hi Arvin,

How long approx. would it take to install a runtime environment on one
computer?
I'm trying to figure out the time to get it up and running on approx.
50 computers.
Would it go on the server?
How about the time to install the front-ends?

What exactly is involved in installing a runtime?
Thanks!

Ric
 
Back
Top