access as frontend to backend sql 2000

[Guest]

Thanks Doug,

But I have continued my search and at last I came across this:
http://msdn.microsoft.com/vstudio/products/vsto/details/default.aspx
There is mentioning of ADE, so it seems VSTO2005 is OK for Access developers.

"VSTO2006": typo, sorry.

Regards,

Jan

 

[Cire via AccessMonster.com]

Dear Cire:

You can use either pass-thru queries, as from an MDB front end, or you may
use an ADP front end, already designed specifically for SQL Server
connectivity.


As to your statement regarding, "what i read on other forums is that it
doesnt support a graphical user interface" I would recommend that you place
the Access front end, which completely defines the graphic interface, on
each front end (client) computer. All that need be passed over the internet
is the data, which improves performance, and this certainly makes the GUI
available for every user. Only raw data need pass between the server and
client, and the client to server communications would be SQL commands, where
are generally shorter than the raw data.

Tom Ellison

Hello all,

[quoted text clipped - 21 lines]

looking forward to your advice
Cheers

Dear Tom

I got one important question. If i were to use pass-through queries, would i
be able to generate reports from the output? i'm still reading up on the
topic but have not found the answer yet. what i mean would be to generate
stuff like pie-charts, bar diagrams to represent the data i've extracted.
Does the mdb report interface support output from pass-through queries as
well?

thanks
Eric

 

[Tom Ellison]

Dear Cire:

A pass thru query will do anything you need. The main difference is that
you cannot use parameters or directly reference controls.

This is easily overcome if you use controls on a form to select what you
would otherwise do with a parameter. Instead of referencing the controls in
a query, you build the SQL for the query using the values in the controls at
that moment, then submit the SQL as a pass-thru.

Tom Ellison

Dear Cire:

You can use either pass-thru queries, as from an MDB front end, or you may
use an ADP front end, already designed specifically for SQL Server
connectivity.


As to your statement regarding, "what i read on other forums is that it
doesnt support a graphical user interface" I would recommend that you
place
the Access front end, which completely defines the graphic interface, on
each front end (client) computer. All that need be passed over the
internet
is the data, which improves performance, and this certainly makes the GUI
available for every user. Only raw data need pass between the server and
client, and the client to server communications would be SQL commands,
where
are generally shorter than the raw data.

Tom Ellison

Hello all,

[quoted text clipped - 21 lines]

looking forward to your advice
Cheers

Dear Tom

I got one important question. If i were to use pass-through queries, would
i
be able to generate reports from the output? i'm still reading up on the
topic but have not found the answer yet. what i mean would be to generate
stuff like pie-charts, bar diagrams to represent the data i've extracted.
Does the mdb report interface support output from pass-through queries as
well?

thanks
Eric

 

[Cire via AccessMonster.com]

Dear Cire:

A pass thru query will do anything you need. The main difference is that
you cannot use parameters or directly reference controls.

This is easily overcome if you use controls on a form to select what you
would otherwise do with a parameter. Instead of referencing the controls in
a query, you build the SQL for the query using the values in the controls at
that moment, then submit the SQL as a pass-thru.

Tom Ellison
[quoted text clipped - 34 lines]

thanks
Eric

ah i see, i must read up on the controls in a form then. by the way do your
have any good access books to recommend? i'm using one now called Access 2002
development unleashed. so was wondering if there are other good alternatives.
i remember i spend an hr trying to find a good book especially one related
to what i'm doing.

Eric

 

[Tom Ellison]

Dear Cire:

What is a good book for you depends on what you already know and what you
need to know. A book that contains mostly things you already know or things
you don't anticipate needing any time soon is not a good choice.

I recommend going to a big city bookstore with a large technical section.
Sit there for an afternoon and try out a dozen titles. Find what fits.

That's what I do, and it has worked very well for me.

Tom Ellison

Dear Cire:

A pass thru query will do anything you need. The main difference is that
you cannot use parameters or directly reference controls.

This is easily overcome if you use controls on a form to select what you
would otherwise do with a parameter. Instead of referencing the controls
in
a query, you build the SQL for the query using the values in the controls
at
that moment, then submit the SQL as a pass-thru.

Tom Ellison

Dear Cire:

[quoted text clipped - 34 lines]

thanks
Eric

ah i see, i must read up on the controls in a form then. by the way do
your
have any good access books to recommend? i'm using one now called Access
2002
development unleashed. so was wondering if there are other good
alternatives.
i remember i spend an hr trying to find a good book especially one
related
to what i'm doing.

Eric

 

[Cire via AccessMonster.com]

Dear Cire:

What is a good book for you depends on what you already know and what you
need to know. A book that contains mostly things you already know or things
you don't anticipate needing any time soon is not a good choice.

I recommend going to a big city bookstore with a large technical section.
Sit there for an afternoon and try out a dozen titles. Find what fits.

That's what I do, and it has worked very well for me.

Tom Ellison
[quoted text clipped - 27 lines]

Eric

Dear Tom,

Thanks for your valuable advice

 

[Cire via AccessMonster.com]

Dear Cire:

A pass thru query will do anything you need. The main difference is that
you cannot use parameters or directly reference controls.

This is easily overcome if you use controls on a form to select what you
would otherwise do with a parameter. Instead of referencing the controls in
a query, you build the SQL for the query using the values in the controls at
that moment, then submit the SQL as a pass-thru.

Tom Ellison
[quoted text clipped - 34 lines]

thanks
Eric

Hi Tom, can you elaborate more on this concept? do u mean using command
buttons/combo/list boxes to build parameters for a SQL statement? which means
VBA prgramming would be needed? If u saw my post in the forms discussion
group, i elaborated my requirements in there. would appreciate if you could
give me advice in that post.

Thanks
Eric