VBA code in Excel will not comoile

[Lou_Reed]

In the attached MS Access 2010 db, I have db with some additional code. I wanted to add a browse button to the form that exports an MS Access table back to
MS Excel 2010.

I have a working set of code that allows one to select a file to import an MS Excel table into MS Access. It works.

I just recycled the VBA code and put in in the VBA code area for the form to export Access tables back to Excel.

It is the same code! I changed the file and the sub name to avoid any ambiguity, but besides that it is the same code.



However, it does not compile it throws an error. I am not sure why.

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[ranman256]

you have
btnBrowse2_Click INSIDE btnBrowse2_Click

remove the outer one. (and the END SUB)

[Lou_Reed]

Okay, I will give it a try. Thanks you.

Respectfully,

Lou Reed

[Lou_Reed]

i tried that and it seemed to not complain. Sorry about being so clumsy before.

My concern now is the new error message, that I get when I try to compile.

I have uploaded a zipped version of this db, plus a screen capture of the error when compiling.

It did not require me to rename the Sub since they are on different forms so I just kept the same name and the same code.

What is the cause of the error? Any help appreciated.

Respectfully,

Lou Reed

[ranman256]

it works fine for me.

[Lou_Reed]

Well, I cannot explain the error message. I will look into it.

I am correct in assuming that I did not have to change the SUB name since I am on a different form?

Respectfully,

Lou Reed

[Lou_Reed]

Well, I have tried it on two different platforms and it does not compile. It still gaga on that line.

MetxtFileName = item

but only on the form for exporting MS Access table to Excel. Where is that file identified or defined?

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[pbaldy]

The sample works fine for me too. You appear to have the code above in the export form, which does not have that textbox. The import form does.

[Lou_Reed]

You got me. I do not see what is missing in the export form's code.

Respectfully,

Lou Reed

[pbaldy]

In the sample, there is no code behind the browse button on the export form. In your picture above, you appear to have it there. The same code in the export form would throw that error, because there is no textbox named "txtFileName" on the export form.

[Lou_Reed]

Okay, I see your point. Actually, I have created code for like this many times and I am surprised at myself.

I have one question. How did you find this out? It seems awfully subtle. Did you just do it by inspection?

Respectfully,

Lou Reed

[pbaldy]

The compile error is telling you it can't find it, so it was my assumption out of the gate. Based on your description and the picture above, I saw you were putting it on a form that didn't have a control with that name. Looking at your sample confirmed it.