There are known risks, even if we don't know exactly what those risks are. So, I suspect that your most useful answer to your question is that it doesn't matter if I've had success with a 10.5 application on Windows 7 my experience may not have a bearing on your application's success on Windows 7. Where your application lies in this n-dimensional spectrum of features and complexity is hard to tell. em DSL / ADSL / Cabo Como voc decidiu visitar esta pgina, h uma boa chance de voc estar procurando pelo arquivo msvcp50.dll ou uma forma de consertar o erro msvcp50.dll est. Tamanho do arquivo: 3,04 MB, Tempo de download: 1 min. Conversely, from what we've inferred from Sybase's behaviour, there exists some combinations and permutations of features that will fail when deployed to Windows 7. Suporta sistemas operacionais como Windows 10, Windows 8 / 8.1, Windows 7 e Windows Vista (64/32 bits). I'm going to go out on a limb and bet that if you created a 10.5 application with one line in the application Open event: MessageBox ('Hello World!', 'It's me!')Īnd deployed this to Windows 7, it would work. (To the best of my knowledge, Sybase never listed those issues in one place, although some probably show up in the bug lists published with each patch.) Support for a new platform is a good feather for your marketing cap, so a reasonable interpretation of this delay is that they found some issues and had to work them out.

It took Sybase to somewhere in the 12.0 cycle to announce that they would support Windows 7.

Windows 7 was released around the PB 11.0 time frame, IIRC. (MS's success with providing forward compatibility is stellar compared to other platforms I've used, but has never been perfect.) Very obviously, any success of 10.5 on Windows 7 is going to rely on Microsoft's ability to provide forward compatibility of applications. I suspect the most useful answer to you is a completely useless answer.įirst point is that PB 10.5 pre-dates Windows 7.

Msvcp50 dll 64 bit win 10