>Hello,
>
>We are experiencing a rather strange problem - we have about 18 DBCs, each containing several hundred remote views. I have a utility which adds a remote view to all these views as we need to.
>
>What I have been noticing over the past few weeks is that some of the older remote views are dropping out of all the DBCs at about the same rate that the newer remote views are being added. When an RV is being dropped from one DBC, it dissappears from all the DBCs (A few times it was only dropped from most DBCs).
>
>Has anyone else seen this behaviour? Is there a limit to the number of RVs a DBC can handle?

Since you haven't had any other replies...I can't find any reference to a physical limitation, although I do think there's a practical one, from the point of view of performance. I tried the following example code. It worked well enough, although I stopped it after 7,932 views were added. MODI DATA isn't advisable at this point and even SET DATA TO took a few seconds.

IF !FILE("TestRemoteConns.dbc")
	CREATE DATABASE TestRemoteConns
ELSE
	OPEN DATABASE TestRemoteConns
ENDIF
SET DATABASE TO TestRemoteConns
* MODIFY DATABASE NOWAIT
LOCAL lni, laViews[1], lnViews, lcView
lnViews = ADBOBJECTS(laViews, 'view')
FOR lni = lnViews TO lnViews + 66000
	lcView = "Remote" + LTRIM(STR(lni,5))
	WAIT lcView + "..." WINDOW NOWAIT NOCLEAR
	CREATE SQL VIEW &lcView REMOTE CONNECTION "Tastrade" AS ;
		SELECT Products.product_name, Products.product_id;
		FROM Products Products
NEXT lni
WAIT CLEAR
CLOSE DATABASES ALL