hannes1
asked on
Access violation......
I have boxed a small VB project (VB6) using the Package and Deployment Wizard that comes with it. When I tested the deployment of the packaged setup files I got the following error: "An access violation occured while copying the file" with the file name specified. Even when I reboxed the project without the file specified in the error above the error will now specify a different file.
I got errors on DLL files like MSVCRT.DLL. Although I don't think the file itself has something to do with it (?)
Any solutions?
What about re-installing VB?
I got errors on DLL files like MSVCRT.DLL. Although I don't think the file itself has something to do with it (?)
Any solutions?
What about re-installing VB?
Indeed you may not have the project opened in the Visual Basic IDE. Because the IDE will lock the .dll file used. if even then you get the error message I suggest that you reboot your system, open the P&D wizard and have specify the correct project.
Regards,
CJ
Regards,
CJ
If you are testing the deployment on a machine that is not your development system, and it is running WinNT or Win2K, make sure the account you are logged in with has local Admin rights.
ASKER
I did the following with no success:
1. Made sure that Setup is the only major app working.
2. Rebooted my PC.
3. Reinstalled VB.
How can this file be locked? I have used P&D alot before without this problem.
????????????????????? I'm confused. Could it be Windows 95?
1. Made sure that Setup is the only major app working.
2. Rebooted my PC.
3. Reinstalled VB.
How can this file be locked? I have used P&D alot before without this problem.
????????????????????? I'm confused. Could it be Windows 95?
It may depends on which OS you are running your setup. I think that Win NT and 2000 don't let you overwrite that dll (since it is used for OS itself).
If problem persist, try to not install it or better, modify setup1.vbp to check if it is already installed, if no install it otherwise no.
If problem persist, try to not install it or better, modify setup1.vbp to check if it is already installed, if no install it otherwise no.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is what I have found out:
I have used the Microsoft Scripting Runtime as a reference (which is the SCRRUN.DLL file) which in turn needs the MSVCRT.DLL file (why I don't know). Both of these are found in the system folder and can't be removed or replaced during the installation process. The problem now comes in that when I don't specify these 2 files to be installed, my program doesn't want to work. Either way I am screwed.
What other way is there to read values from a file (like a text file) that I have created?
Godspeed to all people.
I have used the Microsoft Scripting Runtime as a reference (which is the SCRRUN.DLL file) which in turn needs the MSVCRT.DLL file (why I don't know). Both of these are found in the system folder and can't be removed or replaced during the installation process. The problem now comes in that when I don't specify these 2 files to be installed, my program doesn't want to work. Either way I am screwed.
What other way is there to read values from a file (like a text file) that I have created?
Godspeed to all people.
Have you installed the latest SP for VB?
msvcrt.dll means:
Micro
Soft
Visual
C
Run
Time
And scrrun.dll uses it.
Micro
Soft
Visual
C
Run
Time
And scrrun.dll uses it.
Maybe in the P&D wizard you could specify that these files get installed to your application's directory instead of the system directory.
ASKER
I can't say that I have found the solution and that I have tried everything mentioned. I'll keep trying. I award the points because of your effort to search MS's website (which I hate).
Thank
you
very
much.
Thank
you
very
much.
You must take care of version issue. Before doing any further, check that first!!
ASKER
I have dropped Sequence File Processing and I am going to use Random File Prosessing instead which doesn't need any DLL of any sort. With some work I am sure it will do the job. One thing I have learnt from this is to compile and box my work quite often during the coding process.
Thanks
Thanks
files like msvcrt (visual c++ runtime) are usually not needed and just included for installation on systems that may have an outdated version of this file. I have the habit of not including these files (but i also have the luxury of deploying to a controlled environment where i know what is installed on the PCs i deploy to).