reference will only attach files in current folder

Thanks for the idea. The save relative path is checked. 

Are you using ProjectWise?

ok

The Bentley products will resolve/find the file located in the same folder as the active file first (which is what you are seeing).

The best way around this is to not have the duplicate names.

For a workaround, yes. CADD standards dictate the file naming convention so long term that isn't an option. 
Luckily it is only this one project. I just can't  figure out WHY it's doing this. So irritating.

Thanks for the relies! 

the product was designed that way [don't shoot the messenger ;-) ] - it has always done this.

It just seems strange that a project would have files of the same name. I can see naming conventions IE: Border, Topo, etc... OR even letter designations for different disciplines.

but having files of the same name in one project, I wouldn't consider a very good practice.

I don't think we're on the same page. I've used Bentley products for 15 years and never had this happen. You choose a file to reference, and it attaches regardless of the file name or location it is saved.

We do not have the same named files within one project, I agree, that would be bad practice. Cheers! 

I was just stating the way the product works. Unless I am missing a step in what you have explained.

You have two files of the same name and the issue is that one of the files is either the open design file, or exists in the same folder as the open design file. I cannot tell you why you have never encountered this previously, only why you are encountering it currently.

I hope this helps in determining a workaround or a workflow going forward.

I was just stating the way the product works. Unless I am missing a step in what you have explained.

You have two files of the same name and the issue is that one of the files is either the open design file, or exists in the same folder as the open design file. I cannot tell you why you have never encountered this previously, only why you are encountering it currently.

I hope this helps in determining a workaround or a workflow going forward.

just trying to help.

In this article at the bottom is the order in which the reference is searched:

 Understanding File Locations And Reference Attachments In MicroStation 

Your search is getting to step 4 before the final step 5 of the full path of the reference.

A possible work around might be defining the MS_RFDIR variable to include the folder containing the reference so it is found before the "current" directory ? or attaching the reference using a variable ?

Possibly! I'll check into that variable. I appreciate your help! 

You can create custom variables that point to other folders and make them part of the workset cfg file. For example, if you define a set of variables, such as Project_A and Project_B, you can reference files using Project_A: or Project_B: to force MicroStation to look in the folders pointed to by those variables. There is even a Directory button to select a folder by its variable name - Select Configuration Variable...