cool, i'll give a try, Thanks! ~Timothy T. Rymer

Well, first of all the control doesn't do anything but take in the name and password(it basically looks like a login box), and it's used for more important things. So when they click "OK" or whatever, an event is sent called "Sub Control_Verify()" and that "has to be"(so far) in Client-Side VBScript, so when that happens, can i "fake" a form and submit it automatically (inside of this event)? (which sounds like what you're trying to say....) ~Timothy T. Rymer http://tim.xpertz.com http://www.digipen.edu http://www.ttrx.com

If I am reading this thread correctly than you should be able to use the GROUP BY clause. It does the same thing as DISTINCT but uses a different format. It would look something like: SELECT CUSTOMER_NAME, ID, CHECKED, FOUNDWITH, URL FROM Emails WHERE CHECKED= False GROUP BY CUSTOMER_NAME, ID, CHECKED, FOUNDWITH, URL ORDER BY FOUNDWITH

I believe so, but I've had to put that on the backburner for now, i'll be sure to reply here if I start working on it again (which should be soon, i'm finishing up a more important project right now, so i'm sure i'll be stuck in asp.net land soon enough.) ~Timothy T. Rymer http://tim.xpertz.com http://www.digipen.edu http://www.ttrx.com

Thanks... ~Timothy T. Rymer http://tim.xpertz.com http://www.digipen.edu http://www.ttrx.com

Ed Gadziemski wrote: SELECT CheckDate WHERE CheckDate BETWEEN #??/??/??# AND #??/??/??# should do it. Thanks! I live and learn. Being doing it the hard way all this time :rolleyes: FEI: for SQL users replace the hash/pound, #, with a single quote, '. e.g. SELECT CheckDate WHERE CheckDate BETWEEN '??/??/??' AND '??/??/??' regards, Paul Watson Bluegrass Cape Town, South Africa The greatest thing you'll ever learn is just to love, and to be loved in return - Moulin Rouge Tim Smith wrote: Over here in the third world of humor (a.k.a. BBC America), peterchen wrote: We should petition microsoft to a "target=_Paul" attribute.

Yep. That'd be the one I was on about ;-) :~ (-_-) :~

You are better off passing the recordset object if thats what you are going to be playing with. Otherwise you are using late binding. Something like this : Sub DrawData(ByVal oRec as ADODB.Recordset) Dim dField as Field For Each dField in oRec.Fields MsgBox dField.Value & " " & dField.Name Next End Function Sub Main() Dim oRecord as ADODB.RecordSet Dim ssql as String Dim oConnect As ADODB.Connection oConnect.Open "Blah,Blah" ssql = "SELECT * FROM table1" oRecord.Open ssql, oConnect, adOpenForwardOnly, adLockReadOnly DrawData(oRecord) MsgBox "Success" End Sub

You have to Create the object like this: Dim WithEvents Scriptlet1 as MyScriptlet Set Scriptlet1 = CreateObject("MyScriptlet") Sub Scriptlet1_namechanged MsgBox("Value of name property changed") End Sub Build a man a fire, and he will be warm for a day Light a man on fire, and he will be warm for the rest of his life!

Joaquín M López Muñoz wrote: The real message pump. TradeMark...? ;P :laugh: "An expert is someone who has made all the mistakes in his or her field" - Niels Bohr

Tim, see my aswers bellow , the anonymous and the other :) Joao Vaz

The CComControl class derives by default from CWindowImpl, so the error... About the windowless aspect, i think that by default CComControl window is windowless, so no reason to worry, i think :confused: If isn't windowless, then put this in the private parte of your class: unsigned m_bWndLess:1; , this variable is a member of a union declared in CComControlBase, a base class of CComControl, so it's necessary to declare it in the current class, but i think you wouldn't need this ... Cheers; Joao Vaz

Is the ATL object a COM object, if so then you simply need to declare your class inside of the type library that is created in your idl file of your project. Then you can go to the Project | references menu item in your VB project in order to reference your COM object. From there you can use that object in VB just like any other object. If you are actually exporting an object like you say rather than a function, you would need to instantiate an instance of this object before it can be used, and I do not know of a way to use a C++ object in VB except through COM. If this is what is happening, I am surprised that your program is not crashing.

ATL objects are COM objects. You've got to create an instance of a class to use its functions. In general, you cannot use a member function of your C++ class without creating an instance of that class. It looks like you try to use member functions without creating any variables of that object's type. Volodya Orlenko, orlenko [at] hotmail [dot] com

When you say ATL Class do you mean your dll is a COM server? You already have the means, CreateObject.

sweet thanks i'll try it - it looks like that'll work ~Timothy T. Rymer www.digipen.edu tim.xpertz.com

The exception code is a standard code when using a VB6 component within a process. However, all those exceptions should be handled and not fall into MFC. Andy idea if a VB6 component is loaded into the process?