Ok, the problem that seems to be to me, is that when the spouse isn't online is your code handing it, wouldn't it be easier to save the spouses name.. instead of CHAR_DATA *spouse, use char *spouse.
now the plus of that is you can get the spouses name when the spouse isn't online, but the problem with that is that, if you want some more information of that spouse, you aren't going to be able to access it with out some work. Zartha -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tom Whiting Sent: Saturday, November 10, 2001 7:21 PM To: [email protected] Subject: RE: hrrm %s is for "char *" types, you are supplying "CHAR_DATA *" types. If you want a "temperary" pointer to the char-data, which will only be used in this function for once and not for ever more, then just let it point to the CHAR_DATA of the spouse and do the act with that. Anyway, you have enough pointers now to fix your problem. Originally it was as char, untill things got completely screwed up.. People started losing their spouses, relationship timers weren't updating, people were gaining spouses on remort **boggle**, the whole spousetalk thing was returning "your spouse isn't here" when he/she was... So, I did what I thought would fix the problem, instead of causing a hell of a lot larger one... So, as a perm structure, it was done right, the first time. **ponder** --
