Error 80040112
I am trying to write an app that must print labels as part of its functions. I am using a Windows XP computer and developing tha app on VS2005. I've downloaded and installed the BarTender suite. Since BarTender was previously installed on this computer, the trial period has long expired, but that should just introduce errors into the labels I print on this computer, not prevent me from starting. Does anyone know what error 112 means and what I need to do to fix it?
Nathan Holt
Nathan Holt
0
-
Hi, NathanAtEmcore:
If the trial period has expired, you can not test the functionality properly. I suggest you contact local regional office http://www.seagullscientific.com/aspx/technical-support.aspx or consider purchase if the prior 30 days trial experiences work for you.
Thanks!0 -
We seem to have solved the problem by installing version 8 and using that. I'm still curious about why we needed to do that.
Nathan0 -
Hi, Nathan:
You can send the label format and your sample code to asiatech@seagullscientific.com, I will work with you. I assume you are using ActiveX and add bartender as COM reference. More details http://s3.amazonaws.com/SeagullBarTender/ftp/WhitePapers/WhitePaper_BarTendersActiveXAutomationInterface.pdf
Thanks!0 -
When I was starting this project, I didn't really intend for it to escalate into anything. I never made anything networked in C# (having only used VB6 previously), and nor did I ever make anything even remotely complicated in C#. The idea was just a simple little multiple user chat room, and I didn't understand Sockets at all (I still don't understand anything such as delegates/Asynchronous events/callbacks, as I didn't research them yet since I ended up using Winsock), and just decided to use Winsock at first. I didn't intend for it to actually develop into anything, but it ended up becoming the base for networking for my little game.
Now it just feels too late to change, since I already have 5000+ lines of code. There are certainly things that I can do more efficiently/better, and things besides just Winsock that I'd like to change (using OpenGL instead of GDI+ as GDI+ just seems to have too much limits as to what I can do without it eventually starting to get choppy), but I'm still learning and would certainly like to avoid starting over if possible. I'm not entirely sure how much I would have to change to integrate Sockets instead of Winsock as well. This is the only problem I've had so far with Winsock that I couldn't make a solution to, and even this must have some solution that I could hopefully figure out/fix.0
Please sign in to leave a comment.
Comments
4 comments