| Author |
 Topic  |
|
|
Romee
Junior Member
Netherlands
180 Posts |
 Posted - 08 July 2002 : 05:02:17
|
I think there is a bug in the international version of pop_profile (Post40b03patch004[1]). It regards users of ms sql. I tested it also on access, and there this problem doesnot arise.
It is the old one that you can find in the archive (happy we have one).
http://forum.snitz.com/forum/topic.asp?ARCHIVE=true&TOPIC_ID=13799
In general, the problem is that you don't see the info in the bio field and the other thing is that editing the profile makes that the existing content of the m_quote field and m_LNEWS is not shown, and if one does not notice it, this information is deleted because one posts an empty field. HuwR gave a solution for that, but it doesnot work in ms sql db that I use.
The first thing that has to be changed is the order of lines around line 108.
strMyHobbies = rs("M_HOBBIES")
strMyQuote = rs("M_QUOTE")
strMyLNews = rs("M_LNEWS")
strMyBio = rs("M_BIO")
must be
strMyHobbies = rs("M_HOBBIES")
strMyQuote = rs("M_QUOTE")
strMyBio = rs("M_BIO")
strMyLNews = rs("M_LNEWS")
However I could not find a solution for the other part of the problem.
Romée
Edited by - Romee on 08 July 2002 05:05:53
[moved by bozden on 03 October 2002]
< |
Edited by - Deleted on 03 October 2002 20:15:50 |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 08 July 2002 : 05:13:03
|
This is not exactly a bug in the Snitz code. This more a problem with ADO/database drivers than with Snitz. My test forum, with SQL Server 2000 and OLEDB driver / MDAC 2.7, does not show this problem.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs< |
 |
|
|
Romee
Junior Member
Netherlands
180 Posts |
Posted - 08 July 2002 : 05:23:02
|
Hi Rui,
Is this something I can change?
Romée
< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 08 July 2002 : 05:47:33
|
quote:
Hi Rui,
Is this something I can change?
Romée
Hi Romée,
I don't know what are the database/MDAC version combinations that avoid this. And your host is the one who installs the MDAC in your server. You can always talk to him to see if he can download and install the latest MDAC (it can be found in http://www.microsoft.com/data) and then see if your problem persists.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs< |
|
|
|
Romee
Junior Member
Netherlands
180 Posts |
Posted - 08 July 2002 : 06:12:22
|
They use MDAC 2.70.7713.2, seems rather actual.
(And as you know, my ms sql db is version 7)
Romée
< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 08 July 2002 : 06:20:15
|
quote:
They use MDAC 2.70.7713.2, seems rather actual.
(And as you know, my ms sql db is version 7)
Romée
Yeah, so it seems like the solution to your problem is really to find out the best order for those fields. There was a post from someone else one of these days. I'll find it for you so that you can see if it helps.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
|
Romee
Junior Member
Netherlands
180 Posts |
Posted - 08 July 2002 : 06:46:52
|
Yes!
And for me the suggestion of jinx to change the driver solved the problem.
So it would be a good thing to change the driverline for sql 7 db in the standard config_asp accordingly.
I had a similar problem and switched my connection string to be:
provider=SQLOLEDB;server=SERVER_NAME;uid=UID;pwd=PWD;database=DB_NAME
instead of
driver={SQL Server};server=SERVER_NAME;uid=UID;pwd=PWD;database=DB_NAME
Thanks again!
grz
Romée
Edited by - Romee on 08 July 2002 06:48:59< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 08 July 2002 : 06:56:52
|
quote:
Yes!
And for me the suggestion of jinx to change the driver solved the problem.
So it would be a good thing to change the driverline for sql 7 db in the standard config_asp accordingly.
I had a similar problem and switched my connection string to be:
provider=SQLOLEDB;server=SERVER_NAME;uid=UID;pwd=PWD;database=DB_NAME
instead of
driver={SQL Server};server=SERVER_NAME;uid=UID;pwd=PWD;database=DB_NAME
I tought you were already using an OLEDB driver. OLEDB drivers should always be preferred over ODBC, because they are generally faster and more robust than ODBC drivers. We've been recomending its use for a quite a while.
OLEDB drivers will show as the recomended drivers for SQL server in 3.4.
quote:
Thanks again!
You're welcome  .
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs< |
|
|
|
Deleted
deleted
4116 Posts |
|
| |
Topic |
|
