I might be oversimplifying this explanation, but here goes -

I've got a many-to-many relationship set up so that I can assign the same office to several doctors. The middle table is called 'locations' and that mainly contains info about the doctor pertaining to the office (like a billing TIN, whether he sees new patients or not, etc.....). The viewable info in the 'Office' table contains things like the physical address, telephone # and such......

Everything is working smooth, as far as I can tell. One client is reporting that the locations are somehow duplicating themselves. So now 'all of a sudden' a doctor has 12 locations, when he should only have 4 or something crazy like that. Nothing that I see in the multitude of script and such indicate that the programming or FM is intentionally causing this problem. I have restricted importing only if the tables have no records (all of the importing is done by scripts), so that doesn't seem to be the cause. The user(s) are swearing that they aren't trying to be funny and cause me headaches by creating new locations for the fun of it. The program was created in FMDev 6. The client is using FMServer 5.5 to host the files, and FMPro 6 on each user's desktop. Clients that are using a runtime/single user version of this program are not reporting any kind of problems like this.

All of the other relationships are fine and aren't causing this kind of problem. This is the only one that is set up as a many-to-many in this solution.

Has anyone come across this problem or have had to deal with something simular before? I'm at my wits end trying to figure this out.

Call me arrogant, but whenever a user describes an error to me that i cannot duplicate and cannot account for in my code, i blame them, especially when it's only one client reporting the issue. Maybe they don't realize that when they click the "Duplicate Location" button, that a location will, in fact, be duplicated.

Or maybe it's not so obvious; maybe they're hitting Ctrl-D when they're in the Locations file, thus duplicating that record.

In any case, i would sit down with the client and give a thorough walk-through to the steps they take immediately prior to seeing the duplicate location.

J

Hey, Arrogant, I agree.

Shirley you can't think that's funny.

Alright now, you clowns

This IS the same client who is always complaining about this or that. I now wish that our company never delt with them, but I guess our salesman got over zealous.

I will set up a remote connection so that I can see exactly what they are seeing/doing. Thanks for the insight. If any more ideas come around, I'm more than happy to hear them.

Of course I can, and don't call me Surely.

It seems like the import could be the problem. I would double-check that its testing for all records, not just a found set, or something silly like that.

Well, I have to say that it is very probable that they could be of the all-thumbs crowd. I sometimes wish Ctrl-D were not right next to Ctrl-F, especially when ocassionally using one of those smaller keyboards, where a key is about half the width of one of my big clumsy fingers.