On Wed, Jul 28, 2010 at 3:21 AM, Dave Crozier <[email protected]> wrote: > Jack, > Personally I would steer clear of the General fields as if the ever do get > corrupted you have totally screwed your data and either use the direct link > as you suggest or actualy convert the source file to binary data and store > in a memo field. When you need to view the file then extract it (strtofile() > and filetostr()) creating a temporary file and then processing it. > > I use this technique on SQL Server and it works well. The big bonus is that > you know exactly where the data is i.e in the database as opposed to in a > folder somewhere that can be moved/corrupted etc. > > The only reason to not do it this way is the real possibility of busting the > VFP tible size limit and that is why I went the SQL Server route as > SQLExpress now has a 10gb limit. > > I have only glimpsed at WIA and can't really comment on its suitability. -------------------------
Make a db for just the image table. In your primary db make a view that has the join over to the other db. If size growth is important this will save your bacon a lot faster then you think. If you need multiple image holders have multiple dbs. -- Stephen Russell Sr. Production Systems Programmer CIMSgts 901.246-0159 cell _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
