|
Christopher Duncan wrote: The ODBC based CRecordset stuff turned out to be an absolute freakin' nightmare. Bizarre exceptions thrown, stuff worked in debug but would crash in release, yada, yada
That's a bummer! Sorry I steered you in a bad direction. Apparently the two are not as similar
as I thought.
Cheers,
Mark
|
|
|
|
|
You steered me in a perfectly valid direction! It's not your fault that the quality of Microsoft products is, er... inconsistent. 
I appreciate all the help, man. And if you're ever headed to Atlanta, be sure to throw a guitar in with your bags. 
|
|
|
|
|
Christopher Duncan wrote: And if you're ever headed to Atlanta, be sure to throw a guitar in with your bags.
I'm a drummer, but I'll bring a guitar. I know 2 or 3 chords 
|
|
|
|
|
Mark Salsbery wrote: I'm a drummer, but I'll bring a guitar. I know 2 or 3 chords
Well, I can beat on things but they're usually computers, so quite the pair we'll make.
|
|
|
|
|
Well, like a studio owner/engineer once said to me..."You can't break rock-n-roll"!
It's better that I bring sticks instead.
I'm in Southern California so if you're out this way and need to jam...!
|
|
|
|
|
Hey, I may have to come to SoCal just to party! I need to hit the left coast to hassle Tom in Redmond anyway and collect on some of the pizzas he owes me.
|
|
|
|
|
Christopher Duncan wrote: Hey, I may have to come to SoCal just to party!
Never need an excuse to do that around here 
|
|
|
|
|
|
OLE DB is my preference.
Steve
|
|
|
|
|
Do you happen to know if there's a performance difference between dao, oledb and the CDatabase stuff?
|
|
|
|
|
Sorry, can't help you there. DAO is old and your best off not using it if possible. ODBC is the industry standard but can be accessed via OLD DB. OLE DB is very flexible, COM based and gives you the most options.
Steve
|
|
|
|
|
That's cool. I appreciate the help, man.
|
|
|
|
|
I'd love to see what your app does.
What avantages does it have over lighting console?
Do you find it awkward not having faders to control the light levels?
|
|
|
|
|
Hey, man.
Well, this app came about because Flying Pigs are $30k. And even they don't do everything I want. The light show is designed up front and the lighting events are then triggered by MIDI at show time. So, I don't need a lighting guy (other than the two guys running the follow spots) - the lighting just happens by SFM and I can concentrate on playing guitar and leaping about.
|
|
|
|
|
Nice...
I often wonder how 'on the fly' real lighting shows are these days, I think it comes down to how much time the LD has to prepare and design the lighting before hand, or if they have to 'busk' it with a few pre-prepared macro effects...
So what kind of thing do you use that the hogs don't do?
|
|
|
|
|
Most of the base functionality is the same as hogs or any other decent console - scenes, overlays, focus points, patterns, combos, moving light events, etc. There's only so many tricks in the bag, and all the good systems use them.
However, it's built on a different metaphor. Consoles (physical or virtual) are designed with an LD in mind both at design time and show time, even if they do little more than hit hotkeys to fire off macros or step through a cue list. I designed this from a musician's point of view for those of us who don't have lighting guys at gigs so that you can trigger the events from the stage via footpedal, etc.
I considered selling it as a product once I got it polished, but the thought of providing tech support to, well, musicians...
|
|
|
|
|
Hi,
I need to make an application autorun from a USB device. Can that be done without being dependent on another application on the host system? I have seen some posts in this forum from '03, but it seems the poster never got an answer that I could use for my case.
I would appreciate any help,
Royce
|
|
|
|
|
I am usig VC++ 6.0 with Windows XP Prof. I try to use WinSock commands
<br />
WSADATA wsaData;<br />
iResult = WSAStartup(MAKEWORD(2,2), &wsaData); <br /> when compiled it say undeclared identifier 's
But I did include:
#include winsock2.h
#include ws2tcpip.h
#include stdio.h
(Please notice that I could not put < & > after 3 includes above)
Also in Project ---> Setting ---> Link: I added WS2_32.lib
Anyone knows what I missed defining?
Thanks
|
|
|
|
|
You shouldn't need ws2tcpip.h...it's been rolled into winsock2.h for quite a while.
Which identifiers are showing as undeclared?
|
|
|
|
|
Hi Mark,
I removed ws2tcpip.h (I got it from MSDN example code), but the problem is the same. The undeclared identifiers are all of the two lines that I wrote in my question!
|
|
|
|
|
Are you working from an app-wizard created project or from scratch?
If from scratch, you may need some preprocessor defines before including any windows header files:
#define _WINDOWS
#define WIN32
#ifndef WINVER // Allow use of features specific to Windows 95 and Windows NT 4 or later.
#define WINVER 0x0400 // Change this to the appropriate value to target Windows 98 and Windows 2000 or later.
#endif
#ifndef _WIN32_WINNT // Allow use of features specific to Windows NT 4 or later.
#define _WIN32_WINNT 0x0400 // Change this to the appropriate value to target Windows 98 and Windows 2000 or later.
#endif
#ifndef _WIN32_WINDOWS // Allow use of features specific to Windows 98 or later.
#define _WIN32_WINDOWS 0x0410 // Change this to the appropriate value to target Windows Me or later.
#endif
|
|
|
|
|
I did send you an Email to explain more detail problem!
|
|
|
|
|
No problem.
I would recommend perhaps starting with a wizard-generated Win32 project. Even if it's just
a console app at least it will have all the basic headers set up for you and we can work from
there.
Mark
|
|
|
|
|
Do you mean open a new project with Win32 Appliaction (or Win32 Console Application)? However, I did open both of them ... I saw only a header stdafx.h!
|
|
|
|
|
Right. That stdafx.h, which is used as a precompiled header by default, combined with the
default preprocessor defines in the project settings, have all the basics you need.
You could copy those to your project if you need to and add the winsock2.h include to the
stdafx.h file (at the bottom should be fine).
Whatever it takes...the code should at least compile
Mark
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
