Received: from olympus.scw.org (209-9-156-98.sdsl.cais.net [209.9.156.98]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eAUMMCF19791 for ; Thu, 30 Nov 2000 17:22:12 -0500 (EST) (envelope-from jburton@scw.org) Received: from hades (eos.scw.org [209.9.156.112]) by olympus.scw.org (8.10.1/8.10.1) with ESMTP id eAUMLog07186; Thu, 30 Nov 2000 17:21:50 -0500 From: "Joel Burton" Organization: Support Center of Washington To: Greg Speegle Date: Thu, 30 Nov 2000 17:21:49 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Some advice re:bound/unbound forms for MS Access CC: pgsql-interfaces@postgresql.org Message-ID: <3A268CAD.29805.DE88A0@localhost> In-reply-to: <3A26CAF8.D826C341@10happythings.com> X-mailer: Pegasus Mail for Win32 (v3.12c) X-Archive-Number: 200011/300 X-Sequence-Number: 337 > Can you store binary data in Access tables? Specifically, if I want to > store an image and not keep it anywhere but in Access, how do I do > that? Either: a) as a large object. So all the lo help in the manual. It's a little scattered around, and I'm not clear about all the ins and outs, but it does let you stick large, arbitrary binary stuff in your tables. However, in Access, it doesn't appear as a graphic file or movie, as it would if it were an "OLE Object". Perhaps it can; I've never figured out how. b) as a bytea type. Bytea is a little-known, perhaps little-used field type for binary data. With pg7.0.x, you'll still be limited to 8k rows, but with the magic of 7.1, that restriction is gone. Again, although you can store binary data this way, I don't think it can *appear* this way, as an "OLE Object". Perhaps wiser minds know how. Good luck. -- Joel Burton, Director of Information Systems -*- jburton@scw.org Support Center of Washington (www.scw.org)