We have an app that will be installed in multiple countries. We found out that some on the installations will need to support unicode fields in SQL Server 7.0. We are using a combination of remote views and SQL pass through. Before we run down that road and fall into the blacken endless void, does anyone have an experience with this setup? Do we need to do anything special coding? Can you help us avoid the voids.
Thanx
Fred Lauckner
You know, it works on my computer. I don't know what your problem is.
.Net aint so bad.
