Image BLOBs Please Help!

[PEB]

Are you sure that you have those lines in your sub:


Dim db As Database
Dim T As Recordset

Is this an mdb file or Adp what you use?

[PEB]

Do you have those constants?

Option Explicit
Const BlockSize = 32768

[Mikael]

this is an mdb. I'm just not sure what is going on. I am doing exactly what the article says. Do you have Access 2003?

[PEB]

See if you don't have other global variables in your system named T

Maybe in others modules!

This can do this kind of conflicts!

[PEB]

Yeap this is just on which i've tested it! It works well here!

this is an mdb. I'm just not sure what is going on. I am doing exactly what the article says. Do you have Access 2003?

[PEB]

Try to insert this code in empty mdb file just created...

With only table BLOB and this module...

[MMcCarthy]

Based on the code it seems to be using DAO for the recordsets. Check the following:

Change

Dim T As Recordset

to

Dim T As DAO.Recordset

and

Check that there is a version of the Microsoft DAO library selected in your references list.

[Mikael]

Hello all,

I apologize for my extremely late response. Thank you for all the help, but its still not working. I tried setting T as DAO.Recordset, but now its complaining about:

FileLength = T(sField).Field Size()

Also, I created a blank mdb and put in just the BLOB stuff, and it seemed to work. Whats up with that? I noticed when I compiled the new database it says Compile: db2.mdb (the name of the database), but when I compile the database I'm working in, it says Compile TEST. This is not the name of anything in my database.

[NeoPa]

Hello all,

I apologize for my extremely late response. Thank you for all the help, but its still not working. I tried setting T as DAO.Recordset, but now its complaining about:

FileLength = T(sField).Field Size()

Also, I created a blank mdb and put in just the BLOB stuff, and it seemed to work. Whats up with that? I noticed when I compiled the new database it says Compile: db2.mdb (the name of the database), but when I compile the database I'm working in, it says Compile TEST. This is not the name of anything in my database.

The Compile command changes to reflect the name of your project.
If you hit Ctrl-R to open or switch to your Project Window and select the very top (root) of the tree, you will see the project name. It will very likely be called Test.

[Mikael]

The Compile command changes to reflect the name of your project.
If you hit Ctrl-R to open or switch to your Project Window and select the very top (root) of the tree, you will see the project name. It will very likely be called Test.

You are correct. Thank you. I must have went with a test copy i was working with, and never realized it.

But back to the matter at hand. I created a completely blank database, and the original kb article works fine. BUT, my current db will not work. The error is still the most recent.

[Mikael]

Just wanted to move this article back to the top. If nobody has a solution, how easily can I create a new database, and import all the tables, forms, etc, from my old database?

[NeoPa]

Just wanted to move this article back to the top. If nobody has a solution, how easily can I create a new database, and import all the tables, forms, etc, from my old database?

Using File / Get External Data / Import... you can get all the main objects across quite easily (including Relationships).
Some modules will not copy across this way but that can be done by copy/pasting the code in text form.
Don't forget to duplicate the References too in the VBA window.
Lastly, check Database options and Startup data is duplicated manually.
Guess what - I've had to do that before ;).

[Mikael]

How could I appropriately use the kb article:

http://support.microsoft.com/defaul...;EN-US;Q103257&

I would like to have a field that pulls in jpeg pictures.

[G04]

Hi there,


I also try to save OLE objects in a table and encountered exactly the same errors as Mickael !

In an empty db the KB code works fine.
In the db I am working on was a reference to both DAO 3.6 and also to ADO.
I removed the ADO reference and it worked (I only use DAO).

The error "Type mismatch error 13" lies in the variable T, because of the missing DAO reference or not correctly declaration of variables.

Instead of :

Dim db as database
Dim T as recordset

Use:

Dim db as DAO.database
Dim T as DAO.Recordset

For saving images, I intend to use a separate database and link the table to the main database for storage purposes. A good idea?

Brgds,

[NeoPa]

For saving images, I intend to use a separate database and link the table to the main database for storage purposes. A good idea?

The DAO point is a good one, but already covered in post #22 I think.
The last is a good idea to my mind. I'm no image expert, but if I had to store images in a database I'd definitely try to store them separately from the Front-End db.