Run-time error 3265, but fields do exist!

**jik_ff** · 01-13-2014, 04:08 PM

Ok, I have been at this one for quite a while, and I have to admit that I am new with VBA recordset code...

Here is my code:

Please Login or Register  to view this content.

The table in question has these fields:
AssetName
Categories
Keywords
FilePath

This is copy pasted straight from the table (as I also did with the code). At first I was just adding the AssetName and the Keywords. In this code, that is all that will be added in any case. AssetName has no issue, but it gave the error on Keywords. So I thought that maybe it needs to do the fields in order. So I threw in Categories, but it would give the error on that too. AssetName is the Primary Key... Why are the other fields not recognized as fields in the set?

Eventually, I want to put the value of a control on the page into the Keywords field. I initially had it as such:

!Keywords = me.KeywordPass.value

**jik_ff** · 01-13-2014, 05:07 PM

Face Palm of the day...

Ok, I guess my problem is that I am not getting all the fields with by strSQL statement. I am only getting the AssetName field.... Like I said, I am new with the recordset stuff.... The fix for me was to change my SQL string to:

strSQL = "SELECT [AssetName],[Keywords] FROM [ForProcessing] WHERE [AssetName] = '" & Me.AddAsset & "'"

Go ahead and laugh... I did...

**alansidman** · 01-14-2014, 12:23 AM

I find that a sure way to make sure that your SQL statement in VBA works (when I am having difficulties) is to create it in the QBE and when it returns the expected results, copy the SQL statement into VBA and then delete the query from the QBE. Sounds convoluted, but it does help. Glad you figured it out on your own. Learning is No laughing matter, but it is always good to have a chuckle on oneself.