I concurr - for me it is a bit of hit and miss with array tables with the data and objectID fields - which is the foriegn key; and P generally pick the one the returns no records on the join!
I thing this may not be published as Daemon may think that this is not and issue as all DB access is via the API (which is documented) and therefore unneccessary. Daemon - please reconsider. On Mon, 03 Jan 2005 23:24:50 -0500, Jeff Coughlin <[EMAIL PROTECTED]> wrote: > Gary Menzel wrote: > > I went for a slightly simpler option. > > > > I backed up the table (so I had a quick way to rollback) and then > > manually edited a single entry to see if it all worked OK (which it > > did). > > Good to hear. > > > I recently saw a request for a schema diagram regarding FarCry. And, > > while I do know the schema fairly well, it would be nice to have some > > documentation on it (e.g. how some of the Nav stuff works - i.e. FILE > > root item uses aObjectID's for each file, etc. etc.) > > I agree. I find as a developer that I sometimes need to crawl through > there. A schema would be extremely helpful... perhaps one that is > updated with each Farcry release (since there are usually minor changes > to the DB in each FC release). > > --- > You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] > To unsubscribe send a blank email to [EMAIL PROTECTED] > Aussie Macromedia Developers: http://lists.daemon.com.au/ > --- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
