Replies

Hi Ken,

I tried your problem with a one line Docmd.TransferSpreadsheet on a machine with Vista SP1 and Office 2003 SP2 and could not reproduce it.

Which service packs of Vista and Office 2003 are you running?

Docmd.TransferSpreadsheet does not require Excel to be installed on the machine so this behavior is very odd. Have you seen it with other database on the same machine?

Kevin

Mark,

I use the line numbers in conjunction with the error handling for every piece of code I write, they are by far, the functions I use the most. In my error handling routine I log the error number, error description, line number, procedure name, object name, Access user name, network user name, SQL Server user name (if it

Mark,

I use the line numbers in conjunction with the error handling for every piece of code I write, they are by far, the functions I use the most. In my error handling routine I log the error number, error description, line number, procedure name, object name, Access user name, network user name, SQL Server user name (if it

Pat,

Did you download the pdfEdit995 utility? You can use it to control the output options from pdf995. If you open the pdfEdit995 utility and go to the Auto-Name tab you should have three choices:

1) “Save As” dialog (default).
2) Automatically name the document based on the originating document and save it to the output folder.
3). Save all PDF documents to the same filename.

Options for pdf995 are stored in C:pdf995respdf995.ini, which you can also edit by hand or through code.

Hope this helps.

Pat,

Did you download the pdfEdit995 utility? You can use it to control the output options from pdf995. If you open the pdfEdit995 utility and go to the Auto-Name tab you should have three choices:

1) “Save As” dialog (default).
2) Automatically name the document based on the originating document and save it to the output folder.
3). Save all PDF documents to the same filename.

Options for pdf995 are stored in C:pdf995respdf995.ini, which you can also edit by hand or through code.

Hope this helps.

I heard a rumor that Microsoft acquired some technology from Sagekey that they were including in the next Access Runtime version. Hopefully, MS has licensed enough of the Sagekey scripts so that you can use the MS packaging wizard to install an Access 2003 runtime and not risk damaging any existing Access installations.

I

I heard a rumor that Microsoft acquired some technology from Sagekey that they were including in the next Access Runtime version. Hopefully, MS has licensed enough of the Sagekey scripts so that you can use the MS packaging wizard to install an Access 2003 runtime and not risk damaging any existing Access installations.

I

Hi Richard,

The Access Web has an example of creating irregular shaped forms in Access. It

DBI-Tech

If you are running with Access security enabled you can simply user the CurrentUser() function to get who the user is logged in as. If Access security is not enabled then the CurrentUser() function will always return