Saturday, February 25, 2012
Adobe Export
Currently, no page breaks or repeat header/footer is being used.
Thanks!Your page only needs to be as big as your data on it. I've had that problem
and what I did to fix it was resize my page to fit the layout. I think if
you leave space below or beside your text boxes, the space will show on your
report. I hope this helps.
--Chad
"Terry" wrote:
> What causes blank pages to occur when the report is exported to Adobe?
> Currently, no page breaks or repeat header/footer is being used.
> Thanks!
>|||Your solution to the blank pages being generated when reports are exported to
Adobe worked well.
Thank you so much for your assistance.
"chalexan" wrote:
> Your page only needs to be as big as your data on it. I've had that problem
> and what I did to fix it was resize my page to fit the layout. I think if
> you leave space below or beside your text boxes, the space will show on your
> report. I hope this helps.
> --Chad
> "Terry" wrote:
> > What causes blank pages to occur when the report is exported to Adobe?
> >
> > Currently, no page breaks or repeat header/footer is being used.
> >
> > Thanks!
> >
> >
Thursday, February 16, 2012
ADO erroring under VS2005 that don't occur under VS2003
The following code fragment works when compiled in VS2003 on both Windows XP Pro (32-bit) and WindowsXP Pro x64.
However, when compiled under VS2005, the call to 'pMyRecordsetPtr->RecordCount' fails on both 32bit and 64bit WindowsXP.
I have tried #import'ing msado20.tlb and msado27.tlb.
Has anybody had any similar experience?
HRESULT hr = ::CoInitialize(NULL);
if (FAILED(hr))
{
return false;
}
_ConnectionPtr pConnection;
hr = pConnection.CreateInstance(__uuidof(Connection));
if (FAILED(hr))
{
return false;
}
try
{
//
_bstr_t strConnectionString = "Provider=sqloledb;Server=server1;Database=db1" ;
pConnection->CursorLocation = adUseClient ;
pConnection->Open(strConnectionString,
_T("user"), _T("pwd"), -1);
_CommandPtr pCommand(__uuidof(Command));
pCommand->ActiveConnection = pConnection;
pCommand->CommandText = "MyStoreProcedure";
pCommand->CommandType = adCmdStoredProc;
_RecordsetPtr pRecordSet = pCommand->Execute( 0, 0, 0 ) ;
// This fails
long lNumRecs = pRecordSet->RecordCount ;
pRecordSet->Close();
pConnection->Close();
::CoUninitialize();
}
catch (_com_error &e)
{
::CoUninitialize();
// ...
}
Dear Chappers, I get an error also, but no solution, sorry
Ado.cpp
h:\src\alarmlogger_vc2005\alarmview\debugobj\msado15.tli(111) : error C2065: '_result' : undeclared identifier
ADO erroring under VS2005 that don't occur under VS2003
The following code fragment works when compiled in VS2003 on both Windows XP Pro (32-bit) and WindowsXP Pro x64.
However, when compiled under VS2005, the call to 'pMyRecordsetPtr->RecordCount' fails on both 32bit and 64bit WindowsXP.
I have tried #import'ing msado20.tlb and msado27.tlb.
Has anybody had any similar experience?
HRESULT hr = ::CoInitialize(NULL);
if (FAILED(hr))
{
return false;
}
_ConnectionPtr pConnection;
hr = pConnection.CreateInstance(__uuidof(Connection));
if (FAILED(hr))
{
return false;
}
try
{
//
_bstr_t strConnectionString = "Provider=sqloledb;Server=server1;Database=db1" ;
pConnection->CursorLocation = adUseClient ;
pConnection->Open(strConnectionString,
_T("user"), _T("pwd"), -1);
_CommandPtr pCommand(__uuidof(Command));
pCommand->ActiveConnection = pConnection;
pCommand->CommandText = "MyStoreProcedure";
pCommand->CommandType = adCmdStoredProc;
_RecordsetPtr pRecordSet = pCommand->Execute( 0, 0, 0 ) ;
// This fails
long lNumRecs = pRecordSet->RecordCount ;
pRecordSet->Close();
pConnection->Close();
::CoUninitialize();
}
catch (_com_error &e)
{
::CoUninitialize();
// ...
}
Dear Chappers, I get an error also, but no solution, sorry
Ado.cpp
h:\src\alarmlogger_vc2005\alarmview\debugobj\msado15.tli(111) : error C2065: '_result' : undeclared identifier