Recognising DLL references

Hi,

I posted this on the Land Desktop customisation NG a week ago without
response.
Perhaps the gurus here can shed some light on the possibilities.

When Land Desktop 2004 and 2005 are installed on the same computer, if you
open a DVB file written for R2004 in R2005 the VBA system automatically
changes the reference from the R2004 "LandAuto.tbl" file to the R2005
version of the file.

This, in theory, should make programs written for R2004 and using this
library capable of running in R2005 without a library change by the user.

We have just had a case reported where the opposite has happened.

In R2005 the program is referencing the R2004 file and will not run creating
all the usual "Unable to create Object" type messages..

A repair install of R2005 has been made without effect.

In the interim the program is running after the Land 2005 version of the
file was copied to the R2004 directory (with appropriate backup of the R2004
version of the file).

Has anyone had any experience of this happening and a sensible way of
preventing it ?


--

Regards


Laurie Comerford
www.cadapps.com.au

 

Yeah, one of my guys ran into it and I have since verified it. From my
testing, the issue is not a problem if 2004 is removed prior to 2005 being
installed. It would appear to be an internal issue similar to 2004 ARX
needing re-compiled in VC7 - in thiis case I perssonally think it has
something to do with 2005 being a minor rev [16.1] as opposed to a major
rev [~17].

Anyway, there was a thread about 6 months ago with various alternatives
suggested. In our case, the guy was new and not following our standard
procedure - we write everything strictly in VB and use late binding. This
cured the issue. In my testing, I've come up with either
remove/re-reference or have two different dvbs *IF* its a dual environment.

-- Mike
___________________________
Mike Tuersley
CADalyst's CAD Clinic
Rand IMAGINiT Technologies
___________________________
the trick is to realize that there is no spoon...

 

Laurie: I posted a question on 7-12-04 "Why doesn't this work now???"
regarding DVB's written in 2004 and being opened in 2005.
I had a similar problem with a couple of my programs and the response that I
received from Ravi Pothineni at Autodesk was to open the programs in 2005
and then SAVE them, they would be able to be run in both versions.

--
Matt W

The difference between genius and stupidity is that genius has its limits.
| Hi,
|
| I posted this on the Land Desktop customisation NG a week ago without
| response.
| Perhaps the gurus here can shed some light on the possibilities.
|
| When Land Desktop 2004 and 2005 are installed on the same computer, if you
| open a DVB file written for R2004 in R2005 the VBA system automatically
| changes the reference from the R2004 "LandAuto.tbl" file to the R2005
| version of the file.
|
| This, in theory, should make programs written for R2004 and using this
| library capable of running in R2005 without a library change by the user.
|
| We have just had a case reported where the opposite has happened.
|
| In R2005 the program is referencing the R2004 file and will not run
creating
| all the usual "Unable to create Object" type messages..
|
| A repair install of R2005 has been made without effect.
|
| In the interim the program is running after the Land 2005 version of the
| file was copied to the R2004 directory (with appropriate backup of the
R2004
| version of the file).
|
| Has anyone had any experience of this happening and a sensible way of
| preventing it ?
|
|
| --
|
| Regards
|
|
| Laurie Comerford
| www.cadapps.com.au
|
|
|

 

Did you try it though Matt? And did it work for you? It hasn't at this end
=(
-- Mike
___________________________
Mike Tuersley
CADalyst's CAD Clinic
Rand IMAGINiT Technologies
___________________________
the trick is to realize that there is no spoon...

 

Hi,

The file history is that the raw code was written in R3 Land Desktop.

It was copied to a Win 2000 test computer with Land Desktop R2005 only
installed.

The library files were changed.

The file was saved

The [Debug][Compile] command was run.

The file was saved under a new name

The file was closed

The file from the new name was opened

The file was saved again under it's final name.

(The steps above see the file size vary from about 7Mb up to 10 or 11Mb and
back to 7Mb)

The file was run (part of the code only - to run all the functions takes
hours. However it wont' run with the wrong libraries, so the libraries "had
to be right")

It put into the installation program and installed and run on clean
computers with:

Win 2000 and Land Desktop R2005 only
Win XP and Land Desktop R2005 only
Win XP and Land Desktop R3, R2004 and R2005

The R2004 version is produced with the same process
It has been distributed to several hundred users, none of whom have reported
any problems.

--


Laurie Comerford
CADApps
www.cadapps.com.au

 

Yeah, it worked.
I had to do that for all of our programs while we made the switch from 2004
to 2005 (Land Desktop, Building Systems and Architectural Desktop).

It worked perfectly and we didn't run into any more problems with programs
not running properly.

--
Matt W

The difference between genius and stupidity is that genius has its limits.
| Did you try it though Matt? And did it work for you? It hasn't at this end
| =(
| -- Mike
| ___________________________
| Mike Tuersley
| CADalyst's CAD Clinic
| Rand IMAGINiT Technologies
| ___________________________
| the trick is to realize that there is no spoon...