Search results

sorry to hear that, good luck remembering what you wrote.

what happens if you set a watch to break when some value is true in a procedure that is in that module? Will it open on the break?

Why not just rename it?

Tell your clients to never ever upgrade again? :D

Obviously this is a subjective judgement, but I think that is really feature specific. I think there are many people, including myself, who would agree that moving to 2007 broke a lot of things that worked in 2003. Yeah, they messed a few things up in SP3, but personally I would say that 2003...

I know, the runtime is a total PITA. Good luck!

Maybe its a reference to the flying spaghetti monster? You know, the FSM church?

I don't know, but I couldn't post yesterday - it just hung on me.

Since you sometimes want to print with a value of 0, I don't think it is possible to do what you are asking (maybe someone else knows a way, but I don't). Input boxes are pretty limited. I would suggest creating your own custom form that looks like an input box. Then, instead of using an...

I'm not sure I really understand what you are saying, but if you do if Payment=>0 'your printing code end if then if nothing is entered, it shouldn't print. Is that what you were asking?

Is there any code in the form? Maybe there is code in the on open event that is changing the colors?

You should definitely call SageKey, they helped me solve a huge installation problem (that ultimately was not their fault) awhile back, and they were really nice too.

Have they tried going to the windows update site? That should automatically detect and install whatever it is that they need . . .

glad you got it working

Well, you are going to have to isolate the event that adds a new record - ted martins suggestion above might work. In any case, once you have found the correct event, you need to add the code to insert the value. That will be a currentdb.execute (UPDATE . . .) statement to update the value...

ok, that makes more sense now. So what is the mechanism for adding the new records - is this done through a form or . . .

Oh, so are you actually inserting key values, not names?

That sounds like a poor design - one of the first rules in a relational database is that you shouldn't store data redundantly (like peoples names). You can search for normalization on this forum to read a lot more about it. Do you have any leeway to set up the tables properly?

I wouldn't be too worried - most new systems are delivered quite late, so maybe they will rely on your system longer than you think.

Maybe if you explain a little more about what you are trying to do, you will get more suggestions. For instance, it is difficult for me to grasp why you would need to keep assigning the same names over and over again.