dschrishuhn
asked on
Access 2003 Conversion from 97
Hello,
I have a database that I converted from Access 97 format to Access 2003 format using Tools-->database utilities --> convert database....
It converted with no hangups, but I have an issue. I have a report that I export as text. In Access 2003 the report is truncated after 120 characters per line. Why does it do this and how can I work around it?
Thanks in advance!
I have a database that I converted from Access 97 format to Access 2003 format using Tools-->database utilities --> convert database....
It converted with no hangups, but I have an issue. I have a report that I export as text. In Access 2003 the report is truncated after 120 characters per line. Why does it do this and how can I work around it?
Thanks in advance!
RDWaibel
Take a look at the report. Make sure the text field is allowed to "grow"
ASKER
By "grow" Do you mean expand the size of the report by dragging the margins in design view?
The design is exactly the same as it was in 97 format and it exports correctly. The only thing that changed was the conversion to the 03 format.
He means there is a property on a report text box .. Can Grow (and Can Shrink). Is that set to Yes?
But those properties also existed in 97. But maybe something got hosed in the conversion.
mx
But those properties also existed in 97. But maybe something got hosed in the conversion.
mx
ASKER
They were set to 'no', but so was the original, in 97 format.
I changed them to 'yes' and got closer to the results I need. It gave me all of the data but added a line break at 120 characters, before finishing on the next line. Is there a way to get this all on the same line?
Thank you both for your help so far!
I changed them to 'yes' and got closer to the results I need. It gave me all of the data but added a line break at 120 characters, before finishing on the next line. Is there a way to get this all on the same line?
Thank you both for your help so far!
dschrishuhn,
This is why most devlopers don't export the Report, they export the Report's underlying RecordSource (The table or query)
Furthermore, this "Export Report to Text" option is no longer available in Access 2007.
So it would be best for you to look for an alternative.
;-)
Something like this:
DoCmd.TransferText acExportDelim, , "YourTableOrQuery", "C:\YourFolder\YourFile.tx
Or use something like this, if you need some formatting around the data (query):
DoCmd.OutputTo acOutputQuery, "query43", acFormatTXT, "C:\oeqrf2.txt"
See the help files on "TransferText" and "OutputTo"
;-)
FWIW, I have never had any issue with truncation or Line breaks with TransferText.
;-)
JeffCoachman
This is why most devlopers don't export the Report, they export the Report's underlying RecordSource (The table or query)
Furthermore, this "Export Report to Text" option is no longer available in Access 2007.
So it would be best for you to look for an alternative.
;-)
Something like this:
DoCmd.TransferText acExportDelim, , "YourTableOrQuery", "C:\YourFolder\YourFile.tx
Or use something like this, if you need some formatting around the data (query):
DoCmd.OutputTo acOutputQuery, "query43", acFormatTXT, "C:\oeqrf2.txt"
See the help files on "TransferText" and "OutputTo"
;-)
FWIW, I have never had any issue with truncation or Line breaks with TransferText.
;-)
JeffCoachman
ASKER
Thanks for the suggestions and thanks for the info about 2007. By the time we finish the 2003 upgrades, we're going to probably look at that.
TransferText does not work in this case since I'm with a report. I think it only applies to Tables and Queries.
OutputTo worked as it should, but it still inserts a line break after 120 characters.
Why does it want to start a new line?
TransferText does not work in this case since I'm with a report. I think it only applies to Tables and Queries.
OutputTo worked as it should, but it still inserts a line break after 120 characters.
Why does it want to start a new line?
<TransferText does not work in this case since I'm with a report.>
???
What does "I'm with a report." mean?
I stated that instead of "being with a report", you shjould be exporting ther Report's underlying recordsource (The table or query that the report is based on.)
Did you test the first code snippet?
Again, It has worked perfectly for me for years:
NO truncation and NO Line breaks.
Again, DO NOT EXPORT THE REPORT directly!
Use the code I posted and export the Reports underlying recordset.
Are you saying you tried the code and it did not work?
Please clarify
JeffCoachman
???
What does "I'm with a report." mean?
I stated that instead of "being with a report", you shjould be exporting ther Report's underlying recordsource (The table or query that the report is based on.)
Did you test the first code snippet?
Again, It has worked perfectly for me for years:
NO truncation and NO Line breaks.
Again, DO NOT EXPORT THE REPORT directly!
Use the code I posted and export the Reports underlying recordset.
Are you saying you tried the code and it did not work?
Please clarify
JeffCoachman
ASKER
Sorry for the confusion.
I ran the TransferText and it gave me a CSV-text file. The datasource is a table.
I think I need to export the report in this case because of the design.
Thanks for your suggestions so far.
I ran the TransferText and it gave me a CSV-text file. The datasource is a table.
I think I need to export the report in this case because of the design.
Thanks for your suggestions so far.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The system being used is being grandfather-ed out. Thanks for your time and suggestions
Footnote:
The Export To Excel functionality is back in Service Pack 2 for orffice 2007.
http://www.microsoft.com/downloads/details.aspx?FamilyID=b444bf18-79ea-46c6-8a81-9db49b4ab6e5&displaylang=en
;-)
Jeff
The Export To Excel functionality is back in Service Pack 2 for orffice 2007.
http://www.microsoft.com/downloads/details.aspx?FamilyID=b444bf18-79ea-46c6-8a81-9db49b4ab6e5&displaylang=en
;-)
Jeff