Windows Server

Ravi · Guest

Hello

I have an application that was developed in 16-bit Visual Basic 4.0. Trying
to run the application an Windows 2003 is giving me several GUI problems.

1. The panels from one screen overlap with the panels from previous screen
2. Some labels are rendered transparent.
3. Menus from the previous screen are overlapping with the current screen

4.Thin or "windowless" bitmaps all render as transparent on a form.

5. Panel controlls (threed) also render as transparent.

6. Tab controls show all controls on all panes at the same time with the
areas where a control isn't as transparent.

I was able to run the application properly on windows 2000. It's only on
windows 2003 am I facing these problems

Is there any change in the OS in windows 2003 that is causing this ??

I also tried to set the Compatibilty mode of my 16-bit application to
"windows 95". It did not solve the problem.

Anybody pointers towards the solution are welcomed

--
Ravi Kulkarni
VB Developer

Rebecca Chen [MSFT] · Guest

Hi Ravi,

According to my experience, this behavior shows the application is not
fully compatible with win2k3 system. Win2k3 system has greatly enhanced the
system security, many windows API behavior have also been changed.

It is hard to say what kind of change in win2k3 server cause this issue
since we don't have any clue about how the application is developed.

I suggest you use the following steps to check the status:

Step 1:
============

insert the win2k3 installation CD into the CD-Rom, located to i386 folder
and issue the command:

Winnt32 /checkupgradeonly

Check if win2k3 is compatible with the application. Checkupgradeonly
command will help us to determine the compatibility.If report shows they
are incompatible, I suggest you contact the application vendor to check if
they have the latest version which is compatible with win2k3 server.

For more details about checkupgradeonly command, please refer to the
following link:

Verifying Software and Hardware Compatibility

http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deploy
guide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/de
ployguide/en-us/acicd_sys_edfn.asp

Step 2:
=============

You can also use the Application Compatibility Tools to verify the
compatibility:

Application Compatibility Tools
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deploy
guide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/de
ployguide/en-us/pdpca_appa_hhwq.asp

Step 3:
===================
Check the following two articles to see if they can provide the solution:

Common Compatibility Problems
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deploy
guide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/de
ployguide/en-us/pdpca_appa_hhwq.asp

Application Compatibility Solutions
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deploy
guide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/de
ployguide/en-us/pdpca_appa_hhwq.asp

Any update, let us get in touch!

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Ravi · Guest

Hello Rebecca,

Thanks for the response and appreciate your help.

AS for the application development : This application was developed as a GUI
application in Visual Basic 4.0(16 bit version) on Win95.

In fact this application was developed by us in-house(and we also have the
source code for the same).

I have already looked at the URL'S that you sent me and they did not solve
the problem.

I'm looking at the following options here :

1. Will this application run on win2k3 ? Will it work exactly like it did on
win2000. If not, then we have to stick to win2000 since it has been proven to
work on win2000

2. Is there any changes to the Visual Basic source that we can do to make it
work ?? (I seriously doubt it. After all, how can you make changes to your
source to account for a future release of the OS).But if there is, I would
like to know to see if that option can be pursued

3. Migrate the application to .NET. Obviously this would be ideal option
,but we are unable to pursue this option because of budgetary considerations.

Therefore, the option is for us to get this application working on win2003
without migrating the code base.

You mentioned that the application may not be compatible with windows 2003.
That is true since it was developed using 16 bit visual Basic.

Does this mean that a GUI application which has been developed using a 16
bit tool(VB) will not be functional on Windows 2003 ??

That's the answer that I'm looking for ??

Thank you very much for your time.

Regards
Ravi

"Rebecca Chen [MSFT]" wrote:

Ravi · Guest

Hello Rebecca,

Thanks for the response and appreciate your help.

AS for the application development : This application was developed as a GUI
application in Visual Basic 4.0(16 bit version) on Win95.

In fact this application was developed by us in-house(and we also have the
source code for the same).

I have already looked at the URL'S that you sent me and they did not solve
the problem.

I'm looking at the following options here :

1. Will this application run on win2k3 ? Will it work exactly like it did on
win2000. If not, then we have to stick to win2000 since it has been proven to
work on win2000

2. Is there any changes to the Visual Basic source that we can do to make it
work ?? (I seriously doubt it. After all, how can you make changes to your
source to account for a future release of the OS).But if there is, I would
like to know to see if that option can be pursued

3. Migrate the application to .NET. Obviously this would be the ideal option
, but we are unable to pursue this option because of budgetary considerations.

Therefore, the option is for us to get this application working on win2003
without migrating the code base.

You mentioned that the application may not be compatible with windows 2003.
That is true since it was developed using 16 bit visual Basic.

Does this mean that a GUI application which has been developed using a 16
bit tool(VB) will not be functional on Windows 2003 ??

That's the answer that I'm looking for ??

Thank you very much for your help

Regards
Ravi

"Rebecca Chen [MSFT]" wrote:

Rebecca Chen [MSFT] · Guest

Hi Ravi,

Please see my comments.

1. Will this application run on win2k3 ? Will it work exactly like it did
on
win2000. If not, then we have to stick to win2000 since it has been proven
to
work on win2000.

A: I am not sure whether or not the application will work on win2k3 server.
Please use the checkupgradeonly command as I have mentioned to check the
compatibility. You can download the Win2k3 evaluation version here:

http://www.microsoft.com/windowsserver2003/downloads/trialsoftware/default.m
spx

2. Is there any changes to the Visual Basic source that we can do to make
it work ?? (I seriously doubt it. After all, how can you make changes to
your source to account for a future release of the OS).But if there is, I
would like to know to see if that option can be pursued Does this mean that
a GUI application which has been developed using a 16 bit tool(VB) will
not be functional on Windows 2003 ??

A: Since this is a develop-related question and our group mainly focuses on
the network side, it would be better addressed in the developer newsgroup
since they are the experts in the field.

The developer newsgroups are located at:

http://msdn.microsoft.com/newsgroups/default.asp

Any update, let us get in touch!

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1