Server Change/Pathing Issue

[Anonymous]

Good Day,

About a year ago my company purchased a new server and transferred most of our data onto that server. We went through and did a find/replace in all of our DVB, LISP and other AutoCAD associated files in order to correct pathing issues caused by the server name change. Last week we shut down the old server for good and certain DVB files immediately began to hang up in the load process. After digging through the code I found that it has trouble on the line:

{code}VBALoad \\servername\directoryname\filename.dvb{code}
This led me to believe that we simply missed a path encoded inside that particular DVB. However when I load the file into AutoCAD and search for the old server name, it comes up with nothing. Furthermore when I open the DVB file in notepad it shows numerous references to the old server but when I make changes inside notepad and save the file, I can no longer load it into AutoCAD. I've checked every reference and line of code from inside the Visual Basic Editor to no avail, the only place I am able to find references to the old server is when I open the file in notepad.

I should also note that when the old server is offline the only problem the program has is that loading takes approximately 3 minutes, once the DVB finally loads into AutoCAD everything runs fine. Thanks in advance for any help received.

[Anonymous]

>>However when I load the file into AutoCAD and search for the old server name, it comes up with nothing.

The offending path may not be some text string in code, but an actual reference used by the DVB - say, a custom control, or a routine in a .dll
Check the references in the .dvb. Then check the references of the references. A bit like having xrefs inside of xrefs.


>>the only place I am able to find references to the old server is when I open the file in notepad

A reference in a dvb will not show in the code editor, but it will show up if you peek thru the dvb using notepad/binary editor.
But since the data in the dvb is tokenized, you cant just poke holes in it, using notepad. Its a binary file.

There is also the possibilty that its a dead reference - no longer used, but still in the file, like one might experience in a database.
If thats the case, copy all the code into a new project, repoint the ACTUAL USED references, and save out the new project.
I would do this with the old project open, right beside it, so that you can hunt down the references side-by-side.

Good luck.