MDE file and VBA

[Guest]

I have split my database and I was wondering if the next VBA statement could
couse a problem by compyling the front end database.

combo1.recourdsource="{some sql code}"

after compyling i want to make aa MDE file

Harm Ozinga

 

[Rich Wills via AccessMonster.com]

This will still work I have done the same on many occasions but I would
stress to keep a copy before doing any compiling or making MDE file!! Had
some very unexpected results myself!!!

If you are still not sure then the best would be make a new temp database and
enter the same code and try it out first.

HTH!

Rich

 

[Guest]

It shouldn't, but you have a spelling mistake there
This is yours
combo1.recourdsource="{some sql code}"
It should be
Me.combo1.recordsource="{some sql code}" (drop the u in the record)

So,just incase you have an error, that might be it.

 

[Guest]

Hi, Harm.

It sure will cause a problem. It won't compile, and it will cause a runtime
error, because a combo box doesn't have a Record Source Property (even if you
spelled it correctly). Try

Me!combo1.RowSource = "SELECT * FROM tblScores;"
Me!combo1.Requery

.. . . where "SELECT * FROM tblScores;" is any valid SQL statement. Save it
and compile it, then create the MDE database file.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address so that a message will
be forwarded to me.)
- - -
If my answer has helped you, please sign in and answer yes to the question
"Did this post answer your question?" at the bottom of the message, which
adds your question and the answers to the database of answers. Remember that
questions answered the quickest are often from those who have a history of
rewarding the contributors who have taken the time to answer questions
correctly.