[AccessD] BEU Error

Ok, Here is what the BEU Function beuDBAGetRelations returns for the
relationship name.
 
First Relationship Attempting To Delete. The GUID was created when I set
up the BEU

Works on 2 out of 8 BE's (Including my Dev BE)
{437453F8-115D-4F78-A3EA-D92C48AB93BA}  


Works on 8 out of 2 BE's 
z_RFil5_tblReportFilters_z_RFil5_tblReportFiltersContents_263 

In order for me to get this to work on the 8 BE I tested, I had to
remove the above GUID from within the tblDBAModifyDatabase table and
paste the 2nd string. However, it now does not work on the original 2..
Keep in mind the table & relationship structure is exactly the same
between the BE's


Second Relationship Attempting To Delete. The GUID was created when I
set up the BEU

{EF51A485-8316-40DE-A598-7D7D5C91D890}

z_RFil5_tblReport_z_RFil5_tblReportFilters_262


 Any ideas?? I have over 200 db's, through out the country, that need
this update...:-(

Robert 



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bryan
Carbonnell
Sent: Tuesday, September 13, 2005 6:30 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] BEU Error

On 12 Sep 2005 at 21:34, Robert Gracie wrote:

> Bryan,
>  The BEU will successfully delete the relationship only on the machine

> that the BEU relationship delete sequence was created for, at least 
> that's what it seams.
> 
> In other words, I have a development BE (70 megs)(I test On), that was

> used while setting up the BEU to delete the relationship, all works 
> ok. However on a production BE (6 megs), with the same exact table and

> relationship structure, it fails with error I posted earlier.
> 
>  It seems that the BEU is looking for a specific GUID? (long 
> alphanumeric string) to identify the relationship (instead of using a 
> name combination)and attempts to build the collection based on this 
> GUID. Since this GUID seems to be system specific it of course fails.
> 
>  If I remember correctly I ran into this wall a few years ago, and at 
> the time I figured out away around it, but I can't seem to remember 
> what that solution was, and I'm pretty sure I received that solution 
> from you guys... :-)
> 
>  Does this help?

Robert,

Like Reuben I don't recall this issue either. I have looked through my
e-mails and I can't find any issue that is remotely related to this.

The only thing that I can think of is to copy the actual BE to your dev
box, this should have the relationship name the same as the production
BE. Use this BE to define the relationship delete.

That's as close as a guess I can come up with now. 

And unfortunately Andy is on vacation for 3 week. :(

Sorry,

--
Bryan Carbonnell - carbonnb at sympatico.ca There's a fine line between
genius and insanity. I have erased this line. 


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com