Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post May 11, 2006 04:28 PM by aabruzzese
May 05, 2006 10:37 AM|LINK
You guys convinced me, since I seem to see it at several (imho important) places I finally found the courage to try to combine Club.MDF en ASPNETDB.MDF.
But is it as simple as this:?
1 Delete Club
2 Run club-add.sql
3 Change Web.config:
If this would be the case, could I simply copy the lower Connectionstring and name it ClubsiteDB, so that all instances are pointing to ASPNETDB.MDF?
It would be nice if this was all there is to it, but something tells me that would be too good to be true.
May 05, 2006 04:09 PM|LINK
Here is a good exercise:
Make a new club site from scratch on your local box so you don't risk messing anything up and follow the 5 steps on this page:
Sue has an excellent tutorial here that should hopefully have you wind up with a single database with all the components in it.
May 05, 2006 06:27 PM|LINK
Dit it, and all but one thing seems to work.
Adding Events gives me headaches.
The table is not being filled anymore. All references are to ClubSiteDb now as far as I can see.
Anyone had similar problems with this?
I am out of options with this one.
Thanks in advance,
May 05, 2006 06:50 PM|LINK
What is the error you are getting?
Use the Debug and trace page directives to get a better understanding of the exact error.
May 05, 2006 07:31 PM|LINK
A redirect takes place to Events_List where the event does not show.
The table remains empty as well
May 05, 2006 07:40 PM|LINK
are you logged in ?
Make sure you add the admin user and then log in.
May 05, 2006 07:49 PM|LINK
Somewhere along the line I added a field to enter the cost of a course in Events.
With the new tables that field was missing.
Stumbled against it when looking at Data Connection string,
I guess I need a tracker as well [;)]
Sorry for the bother,
All seems well for now (fingers crossed)
May 05, 2006 07:50 PM|LINK
You know what they say, when there is a will there is a way.
Or was it "He who starts the job is already half done" .
May 08, 2006 03:22 PM|LINK
Cool Lexy ! [cool]
I've wanted to try this for sometime now, put always put it on the backburner.
Wondering aloud... are there any specific circumstances where having a separate membership database is advantageous?
Like if U have multiple websites (2 or more) does having a separate membership database allow members (more smoothly) to use the same user-id/pwd on those multiple websites? [Idea]
Are there any more advantages/disadvantages w.r.t. enabling
single sign-on features across domains etc. ?
Lemme confess, I'm nowhere ready to even having a single fully functional website [:$] (maybe by 2007) but better to be
future-ready,as they say?
Any thoughts as to why it's been designed as 2 cleanly separate DBs rather than a single one ?
In short is there any advantage at all, in NOT combining these 2 DBs??
Nothing critical, muse at leisure. [|-)]
Second-guessings, gut-feelings, intuitive-perceptions and mind-reads are OK too. Sometimes these throw up a 'gem' or two. [;)]
May 08, 2006 08:54 PM|LINK
At this moment I have no sufficiënt knowledge to give you any insight on this,
I work for a foundation (connected to Mental Health Institute) that organises courses, seminars and training. My goal is to get a fully functional site (I felt the standard CSK was the best starting point, but it falls short a bit in some areas)
Like you I am in the process of getting there, trying stuff out. In that process I found out that the users that really contribute something to extend the ClubSite (like Frank and Angelo) both have a combined database.
Since they build the stuff I feel the CSK could use I try to follow their achievements (difficult enough for me I can tell you)
That was my main reason to combine them. Though I can't really give a good reason why it should be combined, I find it even more difficult to find a reason to have them apart. [:)]
Besides that, the two different pages for the member info bug me also. This is one of the things I want to look into as well.