| Author |
 Topic  |
|
|
donos
Starting Member
5 Posts |
 Posted - 05 May 2003 : 00:16:41
|
Hello;
I have run both the MOD setup and alternate setup to create the poll tables FORUM_POLL and FORUM_POLL_VOTES.
There is an error message telling me the table already exists, but I know it doesn't - I'm looking at the Access file in front of me and they aren't there.
Something I'm missing? The other fields were added successfully to tables that are there, so I know it's getting to the right database file.
Don O'Shaughnessy |
Edited by - donos on 05 May 2003 00:18:02 |
|
|
Nikkol
Forum Moderator
USA
6907 Posts |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
|
donos
Starting Member
5 Posts |
Posted - 05 May 2003 : 13:19:05
|
Yes, I recheck the DB every time, and every time it fails.
Interestingly, all the other stuff in the script works just fine - columns added etc. Furthermore, the UNinstall script reports it can't drop the tables because they're not there - go figure, eh?
I worked around the weirdness by manually creating two tables with the appropriate names, then changing the script from CREATE to ALTER. It generates an error because I let Access index one field, but I went in afterward and manually renamed it to POLL_ID.
What I don't know is whether I have all the criteria for tables, fields and such correct - I couldn't intuitively tell that from the script since I don't know the syntax - but the polling function seems to work.
don
|
 |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
|
donos
Starting Member
5 Posts |
Posted - 06 May 2003 : 19:13:52
|
The strConnString is:
strConnString = "bldforum" '## DSN
plain access database
don |
|
|
|
Nikkol
Forum Moderator
USA
6907 Posts |
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 06 May 2003 : 20:12:02
|
| There is a known problem when using DSN connections because admin_mod_dbsetup is unable to ascertain what database you are using |
|
|
|
donos
Starting Member
5 Posts |
Posted - 06 May 2003 : 22:00:50
|
Haven't tried the jet connection because I wanted the db file to be inaccessible.
My cheap kludge seems to have worked since the polling seems to running OK. Are there any changes I should make to the access tables that I don't know about, or should it work OK at this point with a plain jane file ALTERed to add the fields?
On the admin_mod_dbsetup issue, is there any way to telegraph the database type?
don
|
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 06 May 2003 : 23:23:48
|
| The ODBC drivers you use when you pick a DSN connection are slower and less robust than the Jet OLEDB drivers. I see no problem with using a DSNless connection to the DB, though it is recommended that you place the DB file in a folder outside your web root folder. If you do that, I see only advantages in using Jet OLEDB drivers. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
Edited by - ruirib on 06 May 2003 23:36:44 |
|
|
|
donos
Starting Member
5 Posts |
Posted - 07 May 2003 : 12:37:22
|
Would I expect to see this problem persist if I move the DB to SQL Server?
BTW it occurred to me that I could declare the DB via jet to do MOD setups and then revert to DSN once it's in place. Your speed comment makes me think though.
Thanks for the advice.
don
|
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 07 May 2003 : 15:09:23
|
| I don't know whether the problem would persist if you used SQL Server instead. What I know though, is that with SQL server it's even more recommended to use OLEDB drivers, since the speed difference is usually even bigger to ODBC/DSN drivers. The drivers are also more robust. As I usually say, whenever you have an opportunity to use OLEDB drivers over ODBC, do it. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
| |
Topic |
|
Topic Locked
