Yes, a code sample in the MSDN website gives details on how to identify the control that you are using. CMFCToolBarComboBoxButton\* pSrcCombo = NULL; CObList listButtons; if (CMFCToolBar::GetCommandButtons(ID\_EDT\_FIND\_NDC, listButtons) > 0) { for (POSITION posCombo = listButtons.GetHeadPosition(); pSrcCombo == NULL && posCombo != NULL;) { CMFCToolBarComboBoxButton\* pCombo = DYNAMIC\_DOWNCAST(CMFCToolBarComboBoxButton, listButtons.GetNext(posCombo)); if (pCombo != NULL && CMFCToolBar::IsLastCommandFromButton(pCombo)) { pSrcCombo = pCombo; } } }

Beware Web-assisted self-diagnosis especially the sites that require the use of a webcam :suss: Steve _________________ I C(++) therefore I am

I hate to overcharge for services, but in this case, I am tempted to add a few zeros after the normal fee...

Stephen, Your suggestion was exactly what I needed. I used the SetWorldTransform API to rotate and align text along the required axes and let DrawText do the wordwrap part. Thank you very much.

It's the elephant!! No wait, it's the ashtray!! Right?? ;P Smile: A curve that can set a lot of things straight! (\ /) (O.o) (><)

Actually, I had tried that already, it did not work. I am beginning to think this is something so deep inside Microsoft Cursor engine, that there may not be an easy work-around. The SQL I used was not a SHAPE sql anyway. My solution so far has been to switch to a disconnected recordset, and intercept update notifications from the grid. Then I have to write some code for a Lazy Writer to actually update the database with the changes from the grid.

If your printer is 300 DPI, then a 300x300 bitmap will by one inch by one inch. So you need to work out the size of the printer DC, then you can work out how big you need to stretchblt the bitmap. Christian Graus - Microsoft MVP - C++

You'll have to create a new class derived from CDialog. You can of course re-use the dialog resource (IDD_FOO). /ravi My new year's resolution: 2048 x 1536 Home | Articles | Freeware | Music ravib@ravib.com

Okay, I goofed up... The correct value for the Jet OLEDB:Link Datasource is just the name of the database, not the connection string. Oh yes, this will work only for linking to Access Databases. If you are trying to link to a non-Access data source, you need to fill in the "Jet OLEDB:Link Provider String" instead of the Data source. I found this little tidbit at this location: MSDN Page on creating linked tables via ADOX