EVERYONE involved in this project deserves a winning lottery ticket or better!! All I can offer you is my thanks, and hopes that you find a winner on the sidewalk.
I found a small problem with pop_profile.asp that only occurs in a very limited circumstance (I think). The facts:
Server: NT 4.0 SP 6a MS SQL Server 6.5 (must be set to be case sensative [I think]) Snitz Version: 3.3.05
On a new install the members table is created with field "M_HOMEPAGE" (varchar, 50, nullsok) On line 936 of pop_profile the field is referenced as "M_Homepage" which results in the following error:
Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'M_Homepage'.
/pop_profile.asp, line 986
Silly Me... I thought "case sensative" applied to field contents, not name...
quote: We have corrected the case problems in our next release. Usually it only affects Linux/Unix/MySQL installations.
Sorry to post into a locked topic, but it also effect Access/SQL IIS unicode installations with Turkish collating, if the table/field name contains "i" or "I". I had to re-write most of the rs("") calls and strSQL statements in most of the MODs.
Topic Locked
Posted - 06 June 2002 : 17:39:11
