Interested in purchasing if this is possible... :)

[jfoster33702]

I have another app that has a user database already. I want to avoid requiring users to log in multiple times (once for the other app and once for vbulletin..)

I am open to suggestions, but I think the easiest thing would be to disable the registration portion of vB and just ask it to use the cookie/user database from my other application? It could continue to use its internal databases for all other vB tasks.

Any ideas?

Thanks
Jeff

[Erwin]

I have another app that has a user database already. I want to avoid requiring users to log in multiple times (once for the other app and once for vbulletin..)

I am open to suggestions, but I think the easiest thing would be to disable the registration portion of vB and just ask it to use the cookie/user database from my other application? It could continue to use its internal databases for all other vB tasks.

Any ideas?

Thanks
Jeff
What is the other applicatin written with? I assume that it's php and the database is mysql. If that is the case, integrating the two should not be too difficult. You can choose to do either actually. You can hire a programmer to integrate the two for you. It all depends on how integrated you want the 2 to be.

[jfoster33702]

Thanks for the reply - sorry for not providing more infor - Heres the catch - the other app is ASP with an MS SQL2000 DB. The only part I care to integrate/share is username/pw/email. Im just trying to stop users from needing to login twice and/or maintain 2 separate accounts.

Thanks again
Jeff

[Erwin]

Thanks for the reply - sorry for not providing more infor - Heres the catch - the other app is ASP with an MS SQL2000 DB. The only part I care to integrate/share is username/pw/email. Im just trying to stop users from needing to login twice and/or maintain 2 separate accounts.

Thanks again
Jeff
Mmm... I am no expert with ASP or MSSQL... it's probably easier to integrate your membership INTO vB3's user database, if you can export your current membership database into a CVS and then import it... then build your site around vB3.

[jfoster33702]

I cant do that because my other app (auction app) has billing that depends heavily on the encrypted SQL DB.

Jeff

[Brad]

I dont think it would be to hard to write some sort of script in asp or php that will register you in both DB's. For your current members you could move the userdata in vB's mysql database, so both SQL2000 and mySQL have the same user's.

This method would require a user table in both databases for it to work, but it avoids trying to intergrate two seprate databases. Altho it will take up some extra space on the server.