* This is the modus mailing list * Lewis and Suneel,
Thanks for the help with the SQL problems. All is running great now and without the 800Meg of error logs everyday too!!! Do either of you know if this was a faulty script by Vircom or was it user "Ken" error? The only way I could get it to work was by first creating a new database by importing the .mdb file from the Vircom How-To zip file and then using the Query to execute the .sql file. At that time the majority of the error logs were gone with the exception of the "null" trouble. I swear I followed the How-To document to the letter but never seen anything about either of these issues?!?!?!? You guys are the best, Ken Grimes ----- Original Message ----- From: "Lewis Watson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 01, 2003 1:10 PM Subject: [Modus] SQL died and is now rebuilt but needing assistance. > * This is the modus mailing list * > > Hi Mike, > It was Ken's server not mine, I was just trying to help but unfortunately > I was not doing a very good job of reading his entire email and was > preoccupied with my own work. > > In the last email he sent Ken specified that he did not run the script. I > recommended that he run the script and then after getting it working he > should look at using a dedicated user other than SA as SA has much more > permissions that what it really needs to have just for Modus. > Thanks though :-), > Lewis > > ----- Original Message ----- > From: "Mike Herrera" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Sunday, November 30, 2003 7:02 PM > Subject: [Modus] SQL died and is now rebuilt but needing assistance. > > > > * This is the modus mailing list * > > > > Lewis, > > > > Did you run the Vircom sql script when you setup the new SQL? There is > > a script that creates those tables and probably assigns their > > permissions. From what I've read of this thread it got me to wondering > > whether or not you ran the script. > > > > Regards, > > > > Mike Herrera > > Access One Online Svcs. > > http://www.access-one.com > > > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > Behalf Of Ken Grimes > > Sent: Sunday, November 30, 2003 3:11 PM > > To: [EMAIL PROTECTED] > > Subject: [Modus] SQL died and is now rebuilt but needing assistance. > > > > > > * This is the modus mailing list * > > > > Lewis, > > > > Okay my SQL guy is going to be out until Tuesday and I swear I almost > > have it. I did everything on the Vircom How To regarding the SQL script > > but we never ended up with a tblMsgCatalog or a tblRecipients table. > > What I ended up doing was switching to the native mdb file for a short > > time and then copying it over to the SQL machine and creating a new SQL > > database by first importing the mdb and then using the Query to add the > > M3 .sql script. Now I see the two tables named above but now I receive > > an error in the modus logs referring to a field called NewMsg in > > tblMsgCatalog that cannot be null. > > > > T > > > > > > ** > > To unsubscribe, send an Email to: [EMAIL PROTECTED] > > with the word "UNSUBSCRIBE" in the body or subject line. > > > ** > To unsubscribe, send an Email to: [EMAIL PROTECTED] > with the word "UNSUBSCRIBE" in the body or subject line. ** To unsubscribe, send an Email to: [EMAIL PROTECTED] with the word "UNSUBSCRIBE" in the body or subject line.
