Search results

No probs!! the IsNull() function will return a True or False value (case sensitive). so.. If IsNull(var1) = "True" then.....

You can take two aproaches, either test for null values and only update the field if it is not null or replace null values with a zero lenth string "". Hopes this helps

Bulid your query in Access and link the mail merge to that. Then you can specify whatever criterea you want.

Brilliant! Works a treat. For curiousities sake, can you deal with the NULL in the Module. I couldn't get it to work?

It also creates #Error on a NULL string

Genius! I never would have thought to do it like that. Slight mistake on the penultimate line though. I changed it to this and it works. I tend to wing it a bit with modules though. Is my correction right? Public Function CountSpaces(strField As String) As Integer On Error GoTo...

a specific field in each record

I need to be able to count the number of spaces in each record. Any ideas. Cheers

Sounds like a bit of a pain. I don't really have answer to your question but if it's serious problem you may want to look into 'Replication', it has it's pro's and con's, and provide a sololution.

found this as well

Ahh ok I didn't check the spec. You've written "All" but in the spec it tells you to leave it blank if you want to import the whole spreadsheet.

My appologies I thought it was the file name DoCmd.TransferSpreadsheet acImport, acSpreadsheetTypeExcel9, "TFN's 3Q", "c:\Tiger\Marita\Sears\Test.xls", True, All, useoa I've had trouble with specifing worksheet names though, I've found that it doesn't really matter what worksheet name you...

But there's no apostrophie in that file name, so how is it the apostrophie thats making it fail?

There's no apostrophie in that file name. Can you post the line thats failing?

Try useing double quotes to define your file name. DoCmd.TransferSpreadsheet "MyFile'Name.xls"

If LEN([Field]) = 5 then [Field] = '0' & [Field] end if nb field type must be a string

You'd need use SQL and then execute the SQL in VBA docmd.RunSQL (CREATE TABLE TableName)

I don't think there is really much you can do about that. The only thing I could suggest is to compact the database. Tools > Database Utilites > Compact and Repair

Can you explain a bit more about the setup. the impression I get at the moment is that the user selects options which then builds a query 'on the fly' and exports it to an excel file. how are you building the query, are you using creating SQL code behind forms, or in VBA, or passing...

In my opinion your going about the right way, just stick a unique identifier to the end of the name. what I would do though is to use a date/timestamp instead of a compleatly random number, no real reason for this other than it makes the name a bit more relevant. it should be a pretty easy...