Thanks...
but if you look at the image I frequently have two rows for the same client that I want to retain the pattern for.
But no worries, I gave up using it after spending two days with it I ran into an error twice that made me think it was too risky. It kills the database so that it will not open at all, it throws a Runtime 97 error and then hangs the application I can only close it down by killing the process. It does not fix the issue on open, every time I go into design mode with the same form it runs the error.
The first time I thought it was just a random error and applied the same changes to a backup db, after a day working on it the same error occurred. I have had to scrap my second database. When trying to resolve it the first time, I came across this thread, which is exactly the same error I'm getting.
It's a good control in so many ways, but his error is too risky to release it to a client.
Regards,