Access 2003 with Access 2.0

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

One of our clients has a problem with a program (APP A) developed in Access
2003.
He has another software (APP B) which is written in Access 2.0 (yes I know
it is really really old). He run APP A first, then when starts APP B, APP A
is closed by the syetem. Only APP B is running.

My Questions is
Is there any conflicts or incompatible issues between Access 2003 program
(MDE) and Access 2.0 program ?


Thanks a lot to everyone.

Ming
 
Yes. Although I have a seen a report that it worked successfully
against a Novel server

http://groups.google.com.au/group/m..._frm/thread/144c9bc1039d34ac/fa9ece14c448accd

- so it must be something about the server as well as something about
Access 2.0 and Access 2003.

Unless you can find something new, I'm afraid you just can't do that.

(david)
Click to expand...

David,
I guess you are talking about using Access 2.0 linked tables with Access 2003 here ?

IME there are no problems running Access 2.0 apps and also running Access 2003 apps simultaneously on the same PC.
I guess this was what the OP was asking about.

Arno R
 
Ming,

Arno suggests that the two applications might not be using the
same data files.

If that is the case, you need to make sure that they are using
different system workgroups,

and that the system workgroups are in different folders,

and that there are no other databases with the same name but different
extensions,

and that there is no confusion between the folder where Access 2.0
is installed, and the folder where Access 2003 is installed.

You should check the INI file of the APP B (Access 2.0) file to
see what that application is loading

(david)
 
David,

Thanks a lot. I think I didn't state my question clearly. The whole
scenario is like this:
APP A is installed to C:\Program Files\APP-A folder with two files --
APP-A.mde and APP-A_be.MDB. The setup/install file is packed using MS
Access Package and Deploy Wizard. The setup include Access 2003 Runtime.

APP B is installed to C:\APP-B\ folder. APP B setup includes Access
2.0 runtime.

APP A and APP B are two different program and do not share any datafile
(mde/mdb). However, both programs are developped in Access.

APP A does not use any workgroup file.
APP B may use workgroup file.


Ming






--
MCSD,MCDBA, MCSE
http://www.mysoftplus.com



david epsom dot com dot au said:
Ming,

Arno suggests that the two applications might not be using the
same data files.

If that is the case, you need to make sure that they are using
different system workgroups,

and that the system workgroups are in different folders,

and that there are no other databases with the same name but different
extensions,

and that there is no confusion between the folder where Access 2.0
is installed, and the folder where Access 2003 is installed.

You should check the INI file of the APP B (Access 2.0) file to
see what that application is loading

(david)
Click to expand...
 
IMO there should be no problem at all with this scenario.

I can not even imagine that MS did a 'wrong job' with the runtime in this scenario... ;-)
Both app's use totally different dll's, 16 bits vs 32 bits, but you never can tell...
-- Is the problem only one one PC and not on others?
-- Can you test this with full versions instead of runtimes?

Arno R


ming47 said:
David,

Thanks a lot. I think I didn't state my question clearly. The whole
scenario is like this:
APP A is installed to C:\Program Files\APP-A folder with two files --
APP-A.mde and APP-A_be.MDB. The setup/install file is packed using MS
Access Package and Deploy Wizard. The setup include Access 2003 Runtime.

APP B is installed to C:\APP-B\ folder. APP B setup includes Access
2.0 runtime.

APP A and APP B are two different program and do not share any datafile
(mde/mdb). However, both programs are developped in Access.

APP A does not use any workgroup file.
APP B may use workgroup file.


Ming
Click to expand...
 
All Access applications use a workgroup file. If you do not specify
a workgroup file, you get the default workgroup file. You should check
to see what workgroup file is in use by Access 2003.

You would expect that file to have a different extension (.mdw) than the
A2.0 workgroup file (.mda), but they might have the same name (system),
which would cause problems if they were in the same folder.

Also, the A2003 installation might conceivably have picked up the
A2.0 workgroup file - I have seen stranger things.

An A2.0 runtime installation normally includes an INI file in the name
of the application. If not, it will use the default MSACCESS.INI
file. You need to check the INI file to see what is loaded.

Also, :~) what happens if you try to run two copies of the Access 2.0
application? It doesn't just kill all other instances of MSACCESS.EXE
does it? Those database applications were written to run in much
smaller memory spaces.

(david)

ming47 said:
David,

Thanks a lot. I think I didn't state my question clearly. The whole
scenario is like this:
APP A is installed to C:\Program Files\APP-A folder with two files --
APP-A.mde and APP-A_be.MDB. The setup/install file is packed using MS
Access Package and Deploy Wizard. The setup include Access 2003 Runtime.

APP B is installed to C:\APP-B\ folder. APP B setup includes Access
2.0 runtime.

APP A and APP B are two different program and do not share any datafile
(mde/mdb). However, both programs are developped in Access.

APP A does not use any workgroup file.
APP B may use workgroup file.


Ming
Click to expand...
 
Also, the A2003 installation might conceivably have picked up the
A2.0 workgroup file - I have seen stranger things.
Click to expand...

For example, I just re-installed Access 2.0, and now
HKCR\Access.Application.9\Shell\Open\Command
points to c:\Access\MSACCESS.exe



(david)
 
Back
Top