access conversation & installation

[Kumar H.D]

Hi ,

well i have an access 2.x application . I converted it
into access 2000 and then to access 2002 (ie XP). I added
some VBA later . Now i need to create an installable VBA
application of it. I have ms-access professional edition
where in i cont use package & deploy wizard service. I
even cont thing of ms-access 2000 developer edition (MOD)
package & deploy wizard as it will cost me.
So my Question , Is there any other way i can create an
installable setup of my VBA application (ie developed in
access 2002) so that it should be compatiable in win
95,98 and xp and also not neccsary that client
workstation should have access to run my access 2002
application .

Can any one please suggest me on this!!!!!!!

Thanks in Advance

best regards
KUMAR

 

[John Nurick]

Hi Kumar,

The only ways to run an Access application are

1) install Access (either the full version or the free "run-time"
version licenced with the Office Developer Edition) on the workstation

2) use Terminal Services (or similar) and run Access on the server with
a client session on the workstation.

Otherwise, it's a matter of re-creating the application with another
development system, e.g. Visual Basic. There are tools that claim to
convert Access applications to VB, but I've never heard one praised.

 

[Guest]

hi John,

thanks for your reply. You mean to say that either
client m/c shu have access or VBA shu have run-time
access installable .
Is there any other way of creating an MDE file and
making compatible in both win 2000 & xp. I have created
mDE of my VBA ie access 2002 , it works fine in XP only .I
tried running in win 2000 having access 2000 it din't
worked ,some "file format unable to recognise or programm
created in later version " error i received ..

I want my application to be compatibale with win 2000 &
xp ..is this possible ?

Waiting for your reply

Thanks in Advance

best regards
KUMAR H.D

-----Original Message-----
Hi Kumar,

The only ways to run an Access application are

1) install Access (either the full version or the free "run-time"
version licenced with the Office Developer Edition) on the workstation

2) use Terminal Services (or similar) and run Access on the server with
a client session on the workstation.

Otherwise, it's a matter of re-creating the application with another
development system, e.g. Visual Basic. There are tools that claim to
convert Access applications to VB, but I've never heard one praised.

Hi ,

well i have an access 2.x application . I converted it
into access 2000 and then to access 2002 (ie XP). I added
some VBA later . Now i need to create an installable VBA
application of it. I have ms-access professional edition
where in i cont use package & deploy wizard service. I
even cont thing of ms-access 2000 developer edition (MOD)
package & deploy wizard as it will cost me.
So my Question , Is there any other way i can create an
installable setup of my VBA application (ie developed in
access 2002) so that it should be compatiable in win
95,98 and xp and also not neccsary that client
workstation should have access to run my access 2002
application .

Can any one please suggest me on this!!!!!!!

Thanks in Advance

best regards
KUMAR

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.

 

[John Nurick]

Hi Kumar,

According to the Access 2002 help topic "Troubleshoot using an Access
2000 file with multiple versions of Access", MDE files created by Access
2002 use the Access 2002 file format, and Access 2000 cannot open them.

If you want an MDE file usable by either Access 2000 or Access 2002, you
have to create it using Access 2000.

hi John,

thanks for your reply. You mean to say that either
client m/c shu have access or VBA shu have run-time
access installable .
Is there any other way of creating an MDE file and
making compatible in both win 2000 & xp. I have created
mDE of my VBA ie access 2002 , it works fine in XP only .I
tried running in win 2000 having access 2000 it din't
worked ,some "file format unable to recognise or programm
created in later version " error i received ..

I want my application to be compatibale with win 2000 &
xp ..is this possible ?

Waiting for your reply

Thanks in Advance

best regards
KUMAR H.D

-----Original Message-----
Hi Kumar,

The only ways to run an Access application are

1) install Access (either the full version or the free "run-time"
version licenced with the Office Developer Edition) on the workstation

2) use Terminal Services (or similar) and run Access on the server with
a client session on the workstation.

Otherwise, it's a matter of re-creating the application with another
development system, e.g. Visual Basic. There are tools that claim to
convert Access applications to VB, but I've never heard one praised.

Hi ,

well i have an access 2.x application . I converted it
into access 2000 and then to access 2002 (ie XP). I added
some VBA later . Now i need to create an installable VBA
application of it. I have ms-access professional edition
where in i cont use package & deploy wizard service. I
even cont thing of ms-access 2000 developer edition (MOD)
package & deploy wizard as it will cost me.
So my Question , Is there any other way i can create an
installable setup of my VBA application (ie developed in
access 2002) so that it should be compatiable in win
95,98 and xp and also not neccsary that client
workstation should have access to run my access 2002
application .

Can any one please suggest me on this!!!!!!!

Thanks in Advance

best regards
KUMAR

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.

 

[Guest]

OK ........
My heart Felt thanks for your reply ..

thank you

best regards
KUMAR

-----Original Message-----
Hi Kumar,

According to the Access 2002 help topic "Troubleshoot using an Access
2000 file with multiple versions of Access", MDE files created by Access
2002 use the Access 2002 file format, and Access 2000 cannot open them.

If you want an MDE file usable by either Access 2000 or Access 2002, you
have to create it using Access 2000.

hi John,

thanks for your reply. You mean to say that either
client m/c shu have access or VBA shu have run-time
access installable .
Is there any other way of creating an MDE file and
making compatible in both win 2000 & xp. I have created
mDE of my VBA ie access 2002 , it works fine in XP only .I
tried running in win 2000 having access 2000 it din't
worked ,some "file format unable to recognise or programm
created in later version " error i received ..

I want my application to be compatibale with win 2000 &
xp ..is this possible ?

Waiting for your reply

Thanks in Advance

best regards
KUMAR H.D

-----Original Message-----
Hi Kumar,

The only ways to run an Access application are

1) install Access (either the full version or the free "run-time"
version licenced with the Office Developer Edition) on the workstation

2) use Terminal Services (or similar) and run Access on the server with
a client session on the workstation.

Otherwise, it's a matter of re-creating the application with another
development system, e.g. Visual Basic. There are tools that claim to
convert Access applications to VB, but I've never heard one praised.

wrote:

Hi ,

well i have an access 2.x application . I converted it
into access 2000 and then to access 2002 (ie XP). I added
some VBA later . Now i need to create an installable VBA
application of it. I have ms-access professional edition
where in i cont use package & deploy wizard service. I
even cont thing of ms-access 2000 developer edition (MOD)
package & deploy wizard as it will cost me.
So my Question , Is there any other way i can create an
installable setup of my VBA application (ie developed in
access 2002) so that it should be compatiable in win
95,98 and xp and also not neccsary that client
workstation should have access to run my access 2002
application .

Can any one please suggest me on this!!!!!!!

Thanks in Advance

best regards
KUMAR

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.