The only thing my eyes aren't very is "good".

I dated a girl once whose eyes *did* very...I mean vary. They changed
from green to hazel depending on what color she was wearing.

Bill

--- In MS_Access_Professionals@yahoogroups.com, "buffalome90210"
<buffalome90210@...> wrote:
>
>
> But what if my eyes aren't "very" ?
>
>
> Bad joke
>
> Terence
>
> --- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca"
> <wrmosca@> wrote:
> >
> > Terence
> >
> > You can see the SQL for any query. Open the query in design view.
> > Click on View>SQL View. Presto! the complete SQL syntax is right
> > before your very eyes.
> >
> > Bill
> >
> > --- In MS_Access_Professionals@yahoogroups.com, "buffalome90210"
> > <buffalome90210@> wrote:
> > >
> > >
> > > Well yes it helps and no,
> > >
> > > I guess the real answer ( for me any way) is stay away from
> > > macros...I really prefer to know exACTL;Y WHAT THE CODE IS
DOING,
> > AND
> > > WRITINMG A AMCRO AND INCLUDING THEM IS JUST ANOTHER
HOUSEKEEPING
> > > PLACE TO LOOK FOR STUFF AND A SOURCE TO FORGET ONE MORE THING.
> > >
> > > Regarding converting from a macro to sql, I guess what i was
hoping
> > > for was something like, example, I have a texbox attached to a
> > query,
> > > I can go to the row source, open the querry, and right click to
see
> > > the actual sql. Thats What i was hoping for.
> > >
> > > But ty very very much.
> > >
> > > :)
> > > terence
> > > --- In MS_Access_Professionals@yahoogroups.com, "John Viescas"
> > > <JohnV@> wrote:
> > > >
> > > > Terence-
> > > >
> > > > SQL <> Macros
> > > >
> > > > You can certainly execute an SQL query from a macro just like
you
> > > can in
> > > > VBA. Think of Macros as "shorthand VBA." There are lots of
> > > limitations -
> > > > it's hard to work with variables, and loops are very
difficult to
> > > build.
> > > > A2007 has lots of enhancements to macros - introducing
variables
> > > and error
> > > > trapping. In all versions of Access, you can "convert" a
macro
> > to
> > > VBA, but
> > > > not vice-versa.
> > > >
> > > > Does that help?
> > > >
> > > > John Viescas, author
> > > > Microsoft Office Access 2007 Inside Out
> > > > Building Microsoft Access Applications
> > > > Microsoft Office Access 2003 Inside Out
> > > > SQL Queries for Mere Mortals
> > > > http://www.viescas.com/
> > > > (Paris, France)
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: MS_Access_Professionals@yahoogroups.com
> > > > [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of
> > > buffalome90210
> > > > Sent: Monday, January 12, 2009 12:55 PM
> > > > To: MS_Access_Professionals@yahoogroups.com
> > > > Subject: [MS_AccessPros] Stupis macro thingy, Whats more
> > efficient,
> > > macro or
> > > > pure sql code? and also is
> > > >
> > > > I hate myself when I use that macro crap on a form control. I
> > just
> > > feel
> > > > like such looser when I use these automation things as
opposed to
> > > good
> > > > old pure SQL.
> > > >
> > > > BUT, none the less, I get caught up in using them, and they
> > usually
> > > > come back to haunt me somehwre down the line. The question ,
what
> > > are
> > > > the Pro's and Cons of using a Macro vs writing SQL to do the
same.
> > > >
> > > > ALSO, is there a way to display the generated SQL from a
macro ?
> > > >
> > > > TY
> > > > Terence
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > > Yahoo! Groups Links
> > > >
> > >
> >
>