| Author |
 Topic Search  Topic Options
|
yandr 
Groupie
Joined: 10 March 2009
Status: Offline
Points: 106
|
 Post Options
 Thanks(0)
 Quote  Reply
 Topic: Installation woes
Posted: 10 March 2009 at 11:45am |
I tried to install the latest edition (SQL Server 2005) by doing the following - downloaded the package and unzipped it
- created an SQL Server 2005 database on the server and created a user to manage it
- modified the connection string in the webqiz package and uploaded the software
- I tried to run the Web Wiz Forums Database Microsoft SQL Server Setup but I get the following error message
Error entering default values in the Table
tblConfiguration
Invalid column name 'A_Code'.
Invalid column name 'A_Code'.
SQL Server database is set up, but with Error!
The table are created but the thing does not work.
Any ideas?
Edited by yandr - 10 March 2009 at 11:50am
|
 |
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 10 March 2009 at 2:18pm |
|
Most errors are coursed by corrupted files during the upload process.
I would suggest deleting all the tables from the database, reuploaidng the forum files again, and then re-run the database setup on the empty SQL Server database.
|
|
|
|
wb-in-wpb
Newbie
Joined: 16 April 2008
Status: Offline
Points: 17
|
Post Options
Thanks(0)
Quote Reply
Posted: 10 March 2009 at 3:56pm |
|
It could also be the collating sequence for the database. If the database was created case sensitive, and the field somehow was created as a_code instead of A_Code then you could have that problem.
|
|
yandr
Groupie
Joined: 10 March 2009
Status: Offline
Points: 106
|
Post Options
Thanks(0)
Quote Reply
Posted: 13 March 2009 at 8:08am |
|
I found the error in you installation script.
The column is created as A_Code in the create table statement, but when the default value is inserted it is referred to as A_code.
When I fixed this I got the database running.
I dunno why other users haven't reported this error.
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 13 March 2009 at 8:14am |
|
Sounds like your SQL Server database has been setup to be case sensitive which is why you got this error.
It is extremely rare for an SQL Server database to use a case sensitive collation, which is why this has not been reported before.
I would suggest that you use a database that is not setup to be case sensitive as this would prevent other errors like this and also improve searches.
|
|
|
|
yandr
Groupie
Joined: 10 March 2009
Status: Offline
Points: 106
|
Post Options
Thanks(0)
Quote Reply
Posted: 13 March 2009 at 8:19am |
|
Yes, you are right this is the problem and it does come up in lots of other cases.
However, being a software engineer myself, I also consider bad practice to to refer to the same column, table or whatever with randomly assigned uppercase characters.
I would really suggest a fix in future versions.
It is extremely easy to fix this.
Thanks, case closed....
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 13 March 2009 at 9:38am |
|
Have tried to keep all table and field names the same case so that this issue does not happen and the one that you have bought up is fixed for the next release. You should not find any others but if you do then let us know.
Although having a non case sensitive collation would be advisable otherwise if users do searches within the forum system their searches will be case sensitive which may make it harder for them to find what they are looking for.
|
|
|
|
yandr
Groupie
Joined: 10 March 2009
Status: Offline
Points: 106
|
Post Options
Thanks(0)
Quote Reply
Posted: 13 March 2009 at 12:35pm |
|
A workaround if someone needs it, is:
ALTER database [YOURDBNAME] COLLATE Latin1_General_CI_AI
|
|
