Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
compiled in win 7 not working in xp pro.
- Thread starter baran121
- Start date
dilettante
MIS
Can you provide more detail than "not working?"
Windows 7 SP1 broke binary compatibility on ADO classes, which will prevent a program using them from working on anything else but Windows 7 SP1 if you compile there. This is the only issue I can think of right now without more information.
Windows 7 SP1 broke binary compatibility on ADO classes, which will prevent a program using them from working on anything else but Windows 7 SP1 if you compile there. This is the only issue I can think of right now without more information.
- Thread starter
- #3
dilettante
MIS
Can you provide the actual error descriptions you see? With any error numbers if possible?
- Thread starter
- #5
dilettante
MIS
I don't think we even know what the problem is yet. We need more specific information.
baran,
Have you validated the following:
The web.config has the correct values
you can ping the sql server from the XP machine
You are not compiling in 64bit mode, and trying to run on a 32 bit machine.
What error is you application actually throwing?
Lodlaiden
If [blue]you have problems[/blue], I want [green]source code[/green] AND [green]error messages[/green], none of this [red]"there was an error crap"[/red]
Have you validated the following:
The web.config has the correct values
you can ping the sql server from the XP machine
You are not compiling in 64bit mode, and trying to run on a 32 bit machine.
What error is you application actually throwing?
Lodlaiden
If [blue]you have problems[/blue], I want [green]source code[/green] AND [green]error messages[/green], none of this [red]"there was an error crap"[/red]
- Thread starter
- #8
this is the problem which i got.
Have you run Windows update?
In addition, are you using the same version of SQL on both machines?
Are you using ODBC connections?
Do you write to the registry or any other location where permissions may be required?
Are you referencing a file whose version is higher in Windows 7 than Windows XP and thus it cannot be used?
Have you clicked OK to update the files?
If at first you don't succeed, then sky diving wasn't meant for you!
In addition, are you using the same version of SQL on both machines?
Are you using ODBC connections?
Do you write to the registry or any other location where permissions may be required?
Are you referencing a file whose version is higher in Windows 7 than Windows XP and thus it cannot be used?
Have you clicked OK to update the files?
If at first you don't succeed, then sky diving wasn't meant for you!
- Thread starter
- #10
dilettante
MIS
The setup error in your screenshot can be caused by several things. The most common ones are (1.) the system's TEMP folder is not on the system partition and (2.) you are trying to install system files that you should not even have in your package.
Most likely the second one.
Do not try to install bits and pieces of MDAC (msado15.dll, etc.). You have to install the whole MDAC_TYP.EXE package.
However Windows XP already has MDAC anyway, and it is serviced as part of the OS so you should not package it at all. In most cases you should not even package the VB6 runtime.
Most likely the second one.
Do not try to install bits and pieces of MDAC (msado15.dll, etc.). You have to install the whole MDAC_TYP.EXE package.
However Windows XP already has MDAC anyway, and it is serviced as part of the OS so you should not package it at all. In most cases you should not even package the VB6 runtime.
- Status
Similar threads
- Locked
- Question
