I have a network application.  Before, it uses SQL2000 on Win98 OS.  Because of some office upgrading, SQL2000 now runs on an XP platform.  What parameters or, are there any considerations to take, so that the clientside application, running in Win98, can use the DB in SQL2000?

Hi,
I am not aware of any differences between the host environment of SQL2k, however, your connection string will probably have to change as the host name is usually changed. If you are connecting using ODBC, then you don't need to change any client code, just reconnect the client to the server. IF you are connecting using pure ADO/OLEDB then you may need to adjust your connection string (ie. server name, protocol, etc. if applicable).
You will also need to ensure that the SQL2k is registered within the domain of the client and that the user can log in (either integrated security or sql userid/pwd security).

Hope this helps,
Kieron


____________________________
Build it better, faster, quicker, easier.. then fix it (non-offical MS mission statement)

Hello. Though my case is a bit different I post my two cents, too.
I'm working on an MSDE-SQLServer 7.0 db, on several machines. I developed it onto Win98se, or sometimes alternately WinXP Pro, and I locally installed it under Win98se (3 machines), WinMe (1), Win2k (2), XP Home (5), XP Pro (a dozen), and XP 2003 (1 pc). The only other relevant OS on which I didn't test it is Win NT.
It always worked fine, and no changes needed on connection parameters (I even provide my client app the feature to connect either by an INIfile-specified database, or a System DSN, or an .udl file, and everything works: the app automately chooses the first avaliable method).

The only - important - thing I noticed is that just on two XPPro machines (with apparently no reason) it works slow, very slow. The client app has a long delay each time a record is clicked, and even Control Panel's ODBC window takes its time when opening the avaliable servers combo list.
Apparently, the two machines have different software installed, even MSOffice is of two different versions, the only application they both have on board is CR8.5 but all the other machines have it too, as it is part of my setup packet.
After five months of workaround, I solved it yesterday in one machine (my home main pc), by re-installing SQLServer but not without any collateral effect (in one database, the tables are hidden and it says 'No elements', even if above the columns headers is written 'Tables 49 items'. By the way,... Hey, forum: if anybody out there had any hint...). Next week I'll try to reinstall it also in the other machine, but I haven't been able, like none I know, to find out what this peculiar behaviour is due of.
The delay is really relevant, even thirty seconds to load the next record, two minutes to build a simple invoice report: really too long for a local db, and both machines are P4 3Ghz/512Mb, like many other properly-working ones.

Hope it's useful.


(Hey, Mom, it's my 800's post here!!)

[Edited by yronium on 24-08-2006 at 03:30 PM GMT]

____________________________
Real Programmer can count up to 1024 on his fingers

Hi yronium,
If you ever find out - PLEASE post it. I have only ever asked one question on this forum, which was very very similar to the problem you face ( http://www.andreavb.com/forum/viewtopic.php?TopicID=4052&page=0#13766 ) and I never did get an answer. To this day I do not really know, although I did suspect it was something to do with Network priviledges. I just found another way of doing what I wanted, but it still hurts to know I never found out the reason.

By the way - your Mom says she's very proud of your 800 - but how come you don't write home so often !!!      

____________________________
multi-tasking - the ability to hang more than one app. at the same time.

Hello 2U, GeoffS.
It seems to me that it is a really different issue than yours:
my server is local, your one is on a network;
my problem is a performance issue, your one is a granted/denied network permission one (at least, it sounds like it);
I got troubles with SQL Server/MSDE, you got them with MSAccess runtime;
I experienced it only on two machines, with different software equipment, while your two machines seem to have the same equipment installed...
I told you then that I believe it'd be due to some missing/up-to-date/misworking ODBC driver on the second machine, and I'm still convicted of it.

I seem to have solved my one, at least now my app's performances are fine. But I didn't try the other pc yet, as I'll go to that office next week.
It sounded like an obscure SQLServer cache-size setting, and I deduced it by its behaviour when moving from one record to another:
click on one record -> many seconds' delay
after loaded the record, click at once on another -> more seconds' delay
wait for more than fifteen seconds, then select another one -> it's instantly loaded!!
clicked two or three more -> loaded instantly
then again, click another one -> big delay again.
It seemed to need a little relax, like it had to make a clearout of some memory storage, and this would take some time...

Anyway, I seem to have solved it by simply re-installing it. If I find out more, I'll let you know.

PS: say Mom it's vacation time to me (I mean, free time for debugging, ehehe)

____________________________
Real Programmer can count up to 1024 on his fingers