ah, yes I wasn’t sure if you were using a third party library – as you say it’s a common name.
the only update in terms of .h, .cpp, would be to just check that your twain header matches the current one from twain.org.
I would test that code against a different driver. I use and recommend Kodak’s drivers for development. The i30 is a simple enough driver that does almost everything I need to test my code with. Almost any of the drivers you get from Kodak that have ‘i’ as the first letter and are followed by 2 digits (i30, i55) have done almost everything I expect. The main reason I use and recommend them is that outside of having what appears to be the strongest support for the twain specification they support a ‘simulation mode’ where you can run the driver without hardware connected. If you seach the forum you should be able to find a couple of posts where I describe settings up simulation mode – if you need help post back.
Test you open call with the i30, post backwith your success|failure. I seem to remember testing Citrix and I if you have the drivers (the .ds) in the user’s profile that you code works on the desktop that you’ll be fine.
Then I have a question, why twain in citrix? I know why I run twain in citrix but I’m curious why you are. Most solutions don’t need or want to scan from the server room – they want a device in the user’s hand. What is your target?
.