No, not the way I do it. 

I check all parameters for datatype, and for a list of characters (e.g. ";" "," " ' ")  and keywords (e.g. EXEC, DEL, etc )...

Hi Remi,

You may be correct.  But actually I rarely use the bug-prone and verbose ADO syntax anymore.  I find it much easier to use:

rs.open "EXEC mySPname " & param1 &...

Hi again Paul,

Just one other note: It is a LOT of work to convert an MDP to an ADP.  Your forms may look similar, but a lot of the "guts" and...

Please try putting any strings and dates inside single quotes when you call the SP.

HTH,

Rich

I have to disagree with the above suggestions.  I also have seen that ill-advised post (from a non-MS insider, who I will not name) declaring the "death" of ADPs, but there is...

First of all, I think the English was good enough for a web publication, and the article was perfectly understandable despite a few grammatical errors.  I don't think it's fair to...

WADR, Es Que EL always sounds wrong to me, and is too hard to pronounce.  20+ years ago, I thought it was standard to say "sequel."  Nowadays, I think people...

I just tested your problem in an ADP, and I can't reproduce it.  It works fine for me.  The Filters work fine, even if I edit a record in the...

I always make a local copy of my response, because I lose it half the time!

If you really must leave Access, I would go with VB .NET or C#.

But, in my hands, Access ADP development is much, much, much, much more productive than any of the...

Even better, try Stephen Leban's site:

http://www.lebans.com/limitcharsmemo.htm

HTH,

Rich

Seems to me that none of the above approaches will work properly.  I think you need to investigate the DrawTextEx API function, which is not a trivial job.  If you...

Yes, it's not always such a simple answer!

Actually, your boss has a valid point. There are many reasons to prefer SQL code to SPs. I think that too many DBAs buy into the hype, and don't...

Your syntax is wrong.

Use "docmd.openform stdocname" (with a space, not a dot), not docmd.openform.stdocname

The error message is actually correct this time!

The reason it behaves differently on your (development) machine could...