There are a couple of things I would recommend. By default, the PK takes up the one allowed clustered index. In your case, this would appear to be an Identity field that is not even used in this query. I would hazard a guess, based on experience, that the PK field is only used in queries that return a single row rather than queries, such as this one, that return multi-row result sets. If so, you may want to redefine your PK to be nonclustered and then create a clustered covering index. However, the clustered index should be the index that benefits the type of query that most impacts performance. That may or may not be this particular query.
In any event, a covering index, clustered or nonclustered, would benefit you here.
Create (non)Clustered Index IX_TableXXX_Cover1 ON dbo.TableXXX(
CustID Asc,
FormID Asc,
dtmDateAdded Desc
);
Note the datetime field is defined DESCENDING, just as your ORDER BY clause. If this doesn't return a result in 2 seconds or less (average!), let me know.