Replies

But we DO have rights to delete and write to the folder on the network where the db is located. In fact, while logged in on Citrix, I can go to the database and copy it, move it, or delete it just fine. So if compact and repair creates a new database and renames it and deletes the old one, and it is working in the same folder as the original db, and I can manually do those same things, why can’t Access complete the process?

Hans, I would understand if it copies something to the local drive because we don’t have rights there. But I do have full rights on the network drive and the folder where the db lives.

Hans is correct – unless you can get Delete privileges on the network drive where your database is located, doing a Compact and Repair will always create the new database, but is unable to rename it since that involves deleting the original database.

We don’t have rights to copy to the local disk when using Citrix. We can copy to another network drive. I’ve done that without any issues. I’ve even tried doing the compact/repair from a copy on another network drive. It seems to be just when I’m logged into a thin client on Citrix that the problem happens – no matter which network drive I am using and no matter which database.

And, I can open the db on my other computer (not on citrix) and compact/repair there fine.

Thank you, Hans. I am still struggling. Now I am getting the outline where the picture should be, but there’s a red x in the upper left corner. Any ideas about why?

No error. It looks like it’s posting, but then I check and it’s not there. I’m going to try it again now.

No, what exactly is the problem? Do you get an error message? If so, what does it say?

Hans,

I’ve tried posting the reply with the attached file twice so far today. But, it’s not showing up. Did we hit a thread limit or something?

oops. Sorry. You’re right. Here is the correct one. Thank you.

Macropod asked for the mailmerge main document, i.e. the document with the merge fields.
You have attached the result of the mail merge instead.

Sure.

Hi Melanie,

Can you post a copy of the current version of your mailmerge main document, minus any confidential material?

Yes, I followed your instructions, which worked to get the pictures to display. But, not the right pictures. The datasource is a Excel spreadsheet, and each record has its own picture (see attached data source above please). How would I tell the INCLUDEPICTURE field to point to the pictures other than the way I have done it? (I have attached the merge document too above).

Thank you for trying to help me.

Hi Melanie,

Did you follow the steps I suggested for updating the pics after running the mailmerge? If so, and the pictures don’t update correctly, that suggests the INCLUDEPICTURE fields are pointing to the same set of pictures, not to a separate picture for each record. In which case, are you sure the records point to the correct pictures?

Well that sorta worked. I do get pictures, but it’s the same 3 pictures for all the records – they rotate the same 3 pics over and over again for all the records. I can look at the individual pictures and see that each record is numbered to match the data source records.

Well, both the datasource and document are stored in the same folder. The pictures are stored 2 subfolders below the source data and document. Are you saying I need the datasource and document stored in the same folder as all the images?

I don’t do merges, but I took a look at your document. I noticed the file names are generally “relative” to the current folder. However, in the case of a new merge document, that folder may be undefined. You probably need to save the file in the correct location before they can be resolved. Does that help?

omg.. I cannot believe how dense I feel. I fixed the mistakes you pointed out. Now, it has automatically changed my field and it shows the path and file name, and when I preview the merge it still says, Error not a valid file name.

Thank you for your patience. I am sure this is not hard, but somehow I am making this hard.

There are three mistakes:
– The name of the field is INCLUDEPICTURE, not INCLUDE PICTURE
– There shouldn’t be a space before the merge field
– There should be a double quote after the merge field (this error doesn’t occur in your document, only in the post)

So instead of

{INCLUDE PICTURE ” {MERGEFIELD PHOTOGRAPH_FILENAME}’}

it should be

{INCLUDEPICTURE “{MERGEFIELD “PHOTOGRAPH_FILENAME”}”}

I tested it with a picture on my disk.

The data source looks like this:
N:\Test\Jeff Reams\Badging\Photos\00000\574.jpg

My merge code looks like this:

{INCLUDE PICTURE ” {MERGEFIELD PHOTOGRAPH_FILENAME}’}

But when I run the merge, I get “Error! Not a valid filename.”

I’m attaching (hopefully) a sample of the datasource and labels so hopefully you can see what I’m doing wrong.

Thank you.

What does thePHOTOGRAPH_FILENAME field in the data source contain?

– If it only contains the filename without the path, you should specify the path in the INCLUDEPICTURE field. Since you use an absolute path you should *not* use forward slashes but double backslashes:

{ INCLUDEPICTURE “N:TESTJEFF REAMSBADGINGPHOTOS00000{ MERGEFIELD “PHOTOGRAPH_FILENAME” }” }

Note that there is no space between and the { of the merge field!

– If it contains the full path to the picture, you should *not* specify the path in the INCLUDEPICURE field, but you should use double backslashes in path in the data source.

Thank you, but I’m still a bit confused. Do I write out the path for the picture and put the MERGEFIELD PHOTOGRAPH_FILENAME also? I did a screen shot of it both ways and I’m not sure which is right. I went into the datasource and made sure the slashes were forward /.

Well, I did, but I also clicked the button to update all fields and apparently when I saved the file, it lost the fields I hand entered. So, here it is again.

That works beautifully!!! Your instructions were perfect, Hans. Thank youuuuuu!