Post by Steve Eris » Fri, 17 Oct 2003 01:20:50

I have spent some time researching this and came up with
the following workaround...
(I know it's ugly, but it works)

1. Share file #1 into the shared directory.

2. Delete file #1 from the shared directory (Do not purge
the file).

3. Share file #2 into the shared directory.

4. Re-Share file #1 into the shared directory.

At this point VSS will ask you if you want to recover a
deleted file link.
Choose Yes, and VIOLA! you have both files shared.

Hopefully Microsoft will fix this bug soon, but in the
meantime we can do the above.

1. Workaround for Eudora problems caused by email scanning etc. Workaround for Eudora problems caused by email scanning etc.

2. DoCmd.OutputTo MS Access to Excel formatting workaround.

Hello All

I am in the process of developing a small Access database that pulls data
from linked datasources and pushes it through a report and exports into a MS
Excel 97 spreadsheet. Unfortunately when I use DoCmd.OutputTo none of the
orignal formatting applied to the report is exported with the data. I am
using the following VBA code to do this.

DoCmd.OutputTo acOutputReport, strRPT, acFormatXLS, ReportName & "_" &
strDate & ".xls"

I want to find a way to output this data across to MS Excel and then apply
formatting (Using Access VBA) to the spreadsheet so that it is aesthetically
pleasing. Is there a (non-dodgy) way that I can make this happen?


3. textbox maximum character limitation -workarounds

4. Subform on Continuous form workaround?

5. Found Workaround

6. Subform behavior workaround?

7. Shift on Open Disable and Workaround

8. Access / Word Workaround

9. Cannot append workaround question

10. Workaround for Column Naming issue?

11. Additem Workaround in 97/2000

12. KB275090 Alternative workaround

13. Workaround: ...because it doesn't satisfy the criteria in the underlying record source

14. Workaround Security message "...trying to automatically send e-mail

15. Autonumber Workaround with SQL Server 2005 BE