Database questions

  • Thread starter Thread starter Tom Gahagan
  • Start date Start date
T

Tom Gahagan

"Kevin Spencer" wrote in message
First, what exactly is an "ODBC Link?"
Click to expand...


< putting smart ass answer cap on >
From MS Help.....
Open Database Connectivity (ODBC) for Database Connectivity
Open Database Connectivity (ODBC) technology provides a common interface for
accessing heterogeneous SQL databases. ODBC is based on Structured Query
Language (SQL) as a standard for accessing data. This interface provides
maximum interoperability: a single application can access different SQL
Database Management Systems (DBMS) through a common set of code. This
enables a developer to build and distribute a client/server application
without targeting a specific DBMS. Database drivers are then added to link
the application to the user's choice of DBMS.

ODBC's flexibility is illustrated by the following features:

a.. Applications are not tied to a proprietary vendor API.
b.. SQL statements can be explicitly included in source code or
constructed on the fly at run time.
c.. An application can ignore the underlying data communications
protocols.
d.. Data can be sent and received in a format that is convenient to the
application.
e.. ODBC is designed in conjunction with the emerging international ISO
Call-Level Interface standard.
f.. There are ODBC database drivers available today for 55 of the most
popular databases.
< putting smart ass answer cap off > :)

Tom Gahagan
 
I'm just getting started with databases in FP2003. I'm running a Wk2 Server
(where my pages are posted to) and doing my development on a XP Pro machine.
I set up a ODBC link on my server for the database I created. My question
is this, how do I get to see that ODBC connection on my XP Pro box where
FP2003 is running?

In my 'site settings' it tells me that 'no server is currently in use'.
Does this need to change in order for me to see the connection? And if so,
how do you change that?

Thanks!!
Steve
 
You have to create a connection on your local machine that same as the
connection you have created on your server. So under Windows XP Pro you also
need to be using IIS.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================
 
First, what exactly is an "ODBC Link?" Are you referring to a System DSN? If
so, you need to have a System DSN with the same DSN name on your local
development machine and the remote server. The DSN name is what FrontPage
uses to connect. Without the same named DSN on your dev machine you won't be
able to test.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
http://www.takempis.com
Big Things are made up of
Lots of Little Things.
 
-----Original Message-----
I'm just getting started with databases in FP2003. I'm
running a Wk2 Server (where my pages are posted to) and
doing my development on a XP Pro machine. I set up a ODBC
link on my server for the database I created. My
question is this, how do I get to see that ODBC
connection on my XP Pro box where FP2003 is running?

In my 'site settings' it tells me that 'no server is
currently in use'. Does this need to change in order for
me to see the connection? And if so, how do you change
that?
Click to expand...

If you haven't already done so, you'll need to install IIS
on your Win XP Pro box, publish your Web to that location,
open it via HTTP as in http://127.0.0.1, and then set up a
local database connection.

IIS is an option under Control Panel, Add/Remove Programs,
Add/Remove Windows Components. Be sure to run Windows
Update after installing.

Jim Buyens
Microsoft FrontPage MVP
(e-mail address removed)
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*
 
So basically I have to have IIS running on 2 machines, even though they're
sitting right next to each other?

I'm guessing that I publish to my development machine running IIS to test,
and with the extact same settings in IIS, publish to the web server when
everything works correctly?

Steve
 
Steve Grosz said:
So basically I have to have IIS running on 2 machines, even though they're
sitting right next to each other?
Click to expand...

Yes. The code that accesses the database and presents data in theWeb
page has no way of running when you browse the page from disk. You
have to browse the page from the Web server, and then the Web server
detects and runs your code.

So if you want separate test and production environments, you need
separate Web servers.
I'm guessing that I publish to my development machine running IIS to test,
and with the extact same settings in IIS, publish to the web server when
everything works correctly?
Click to expand...

You could do that, but most developers just work directly on the test
web server. You open the http:// Web site in FrontPage or Visual
Studio, write your code, and test.

Jim Buyens
Microsoft FrontPage MVP
(e-mail address removed)
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*
 
LOL! Whew.... can't take a little good natured kidding can you Kevin?

It seems pretty plain that the person used "link" in place of connection.
NOT that difficult to decipher.

Oh well.... best wishes to you and keep up the good work.

Tom Gahagan
 
I'm sorry, Tom, but I didn't see the term "ODBC Link" in any of that.
Perhaps you can point it out to me. And perhaps you can tell me whether the
original poster was referring to a System DSN, ADO Connection String, or a
FrontPage Database Access page.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
http://www.takempis.com
Big Things are made up of
Lots of Little Things.
 
Didn't mean to be thin-skinned, Tom. :)

It's the programmer in me. I am trained NOT to assume anything. Nobody knows
the correct terminology for everything, but if one doesn't know the correct
terminology to identify something, it is better to describe it fully than to
simply make up a subjective term. As I pointed out, the term "ODBC Link" can
mean any of a number of things, and in diagnosing a problem accurately, it
is important to know which of those things one is describing. This can be
achieved with a little bit of description, which is much better than an
off-the-cuff invented term.

For example, I have seen the term "database connection" used in a dozen
different ways in this newsgroup, to describe everything from the Connection
String in the global.asa file to a System DSN, to an ASP page. "link" is a
similar term. People come from all over the world, and use different words
in different places to describe different things. Technical terminology
exists for the purpose of clarifying communication. And while one doesn't
have to know the technical term for something in order to identify it, one
should at least supply enough information to make the identification.
Substituting one invented term for another describes nothing.

Therefore, when I see an ambiguous term, I ask for clarification.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
http://www.takempis.com
Big Things are made up of
Lots of Little Things.
 
Back
Top