Postal Code.

Can any one help me regarding the postal code. As we have seen in the
website we put postal code and it will display the nearest distance... can
any one help me out regarding this ... like what would be the formula to
calculate the distance...
I would highly appreciate.
Thanks
Rogers wrote:
> Can any one help me regarding the postal code. As we have seen in the
> website we put postal code and it will display the nearest
> distance... can any one help me out regarding this ... like what
> would be the formula to calculate the distance...
> I would highly appreciate.
> Thanks
I think you'll need latitude and longitude to do the calculation. See
this page for an example:
http://px.sklar.com/code.html/id=1062
You can buy the database here:
http://www.zipcodeworld.com/
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Yeah but they do not have the long lats.
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:eHyMDbKuFHA.1132@.TK2MSFTNGP10.phx.gbl...
> Rogers wrote:
> I think you'll need latitude and longitude to do the calculation. See this
> page for an example:
> http://px.sklar.com/code.html/id=1062
> You can buy the database here:
> http://www.zipcodeworld.com/
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com

Post update for SQLServer SP2--is there one for SQLServer Express?

Regarding KB935356, is there a "post" service pack 2 update for SQLServer Express?

Thanks.

hi,

LizWard wrote:

Regarding KB935356, is there a "post" service pack 2 update for SQLServer Express?

Thanks.

I'm currently at 3159 build (both on SQL Server 2005 Dev editions and SQLEpxress), so I did not install 3161, but the "Applies to" section reports SQLExpress and SQLExpress With Advanced Services as well, so you should be able to install it on them, as long as you really need them and contact Microsoft for it..

regards

|||For SQLExpress, you stated that you are currently on build 3159. Where did you get that build from? I'm currently on this version:

9.00.3042.00.

I downloaded what seemed to be the latest SQLExpress...please send the URL that you used.

Thanks very much.

|||

hi,

it's "linked" above in the "3159" word

anyway, it's at http://support.microsoft.com/default.aspx/kb/934459/en-us

regards

|||

Andrea:

There is a later one: http://support.microsoft.com/kb/935356/en-us which is Build 3161 -- Article dated 4/19/2007.

Our company has that one downloaded so I will try it when I go "off call" next Wednesday.

Thanks for your help....I hope it will work on SQLExpress.

Lisa

|||

Andrea:

I was able to apply the hotfix that I mentioned in my post on 4/19. Sorry for the delay in replying.

Thanks for your help.

Lisa

sql

Post update for SQLServer SP2--is there one for SQLServer Express?

Regarding KB935356, is there a "post" service pack 2 update for SQLServer Express?

Thanks.

hi,

LizWard wrote:

Regarding KB935356, is there a "post" service pack 2 update for SQLServer Express?

Thanks.

I'm currently at 3159 build (both on SQL Server 2005 Dev editions and SQLEpxress), so I did not install 3161, but the "Applies to" section reports SQLExpress and SQLExpress With Advanced Services as well, so you should be able to install it on them, as long as you really need them and contact Microsoft for it..

regards

|||For SQLExpress, you stated that you are currently on build 3159. Where did you get that build from? I'm currently on this version:

9.00.3042.00.

I downloaded what seemed to be the latest SQLExpress...please send the URL that you used.

Thanks very much.

|||

hi,

it's "linked" above in the "3159" word

anyway, it's at http://support.microsoft.com/default.aspx/kb/934459/en-us

regards

|||

Andrea:

There is a later one: http://support.microsoft.com/kb/935356/en-us which is Build 3161 -- Article dated 4/19/2007.

Our company has that one downloaded so I will try it when I go "off call" next Wednesday.

Thanks for your help....I hope it will work on SQLExpress.

Lisa

|||

Andrea:

I was able to apply the hotfix that I mentioned in my post on 4/19. Sorry for the delay in replying.

Thanks for your help.

Lisa

Possible to insert a page break?

I have a question regarding page break. Is there a way to add a page break
before a text box?
I know you can do this with tables, but I need to have the textbox which
contains the table title to start at the top of the page, instead of the
table itself. Thanks.
-JosephI'm not sure I understand the issue correctly, but did you try putting the
textbox inside a rectangle and add the page break on the rectangle?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Joseph" <Joseph@.discussions.microsoft.com> wrote in message
news:72370566-0AAA-435C-B376-F16064A3D9EF@.microsoft.com...
> I have a question regarding page break. Is there a way to add a page
break
> before a text box?
> I know you can do this with tables, but I need to have the textbox which
> contains the table title to start at the top of the page, instead of the
> table itself. Thanks.
> -Joseph|||Rectangle solves my needs. Thanks Robert.
Joseph
"Robert Bruckner [MSFT]" wrote:
> I'm not sure I understand the issue correctly, but did you try putting the
> textbox inside a rectangle and add the page break on the rectangle?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Joseph" <Joseph@.discussions.microsoft.com> wrote in message
> news:72370566-0AAA-435C-B376-F16064A3D9EF@.microsoft.com...
> > I have a question regarding page break. Is there a way to add a page
> break
> > before a text box?
> >
> > I know you can do this with tables, but I need to have the textbox which
> > contains the table title to start at the top of the page, instead of the
> > table itself. Thanks.
> >
> > -Joseph
>
>

possible bug regarding single line comments in SQL Server Management Studio

I don't know if this is a bug or something I've messed up in my settings. I am using SQL Server Management Studio with SQL 2005 service pack 1 installed, and I've been using it successfully ever since SP1 came out. All of a sudden, any time I have a query with a single line comment (i.e. using dash dash -- ), the rest of the query is ignored as if the single line comment is really a multi-line comment without the closing */

An example:

select top 100 *

from myTable

-- this is a comment

where myTableID = 1234

This would normally return exactly one row, but instead returns 100 rows ( as if the where clause did not exist). If I move the where clause above the comment, it works as expected. Any ideas?

In trying to fix this, I've uninstalled and reinstalled and even reinstalled SP1, but it still isn't fixed.

You've got me stumped. I took the code you have posted and it ran fine for me.

Can you post the exact code that you are using? Maybe we'll see that hanging character you missed or somthing.

|||

I used the exact query, merely changing the table name and ID column.

I ended up going through the process yet again (uninstalling the tools, reinstalling the tools, then installing SP1) and rebooted but still had the problem. However, after a second reboot, it starting behaving properly again. I hope my problem does not resurface.

|||We (me a colleague of mine), have withnessed this same behaviour and, atfer some deep analysis, we have concluded that this bug arises when the Transact-Sql line terminates with a CR (Carriage Return, Ascii(13)) only charaters when it should terminate with both CR (Carriage Return, Ascii(13)) followed by an LF (Line Feed, Ascii(10))

It seems that once SqlServer reachs a single-line comment identifier (--) it keeps fetching bytes untill a compounded line termination (CR followed by LF) is reached.

In the following sample, the {CR+LF} and {CR} are representations of their respective invisible ascii codes.

--This is just a normal single-line comment {CR+LF}
SELECT 'This command works fine' {CR+LF}

--This is a buggy single-line comment {CR}
SELECT 'This command does not work'{CR}
SELECT 'This command does not work either' {CR+LF}
SELECT 'This command work fine too' {CR+LF}

Moreover we have reasons to bellieve that this bug resides in Query Editor provided with SQL Server Management Studio Express Edition (at least, this was version my colleague was using when this bug arose). Anyway, although this bug must be corrected, LF should just be ignored when dealing with Sql scripts.

Running software:

SQL Server Management Studio Express Edition

Ms SQLServer 2000 (8.0.2039)

Win XP Portuguese SP2

Getting this sample you can:

- Load and execute it, using QueryAnalyzer to see the refered behaviour;
- View it, using Notepad, to see what actually happened.

possible bug regarding single line comments in SQL Server Management Studio

I don't know if this is a bug or something I've messed up in my settings. I am using SQL Server Management Studio with SQL 2005 service pack 1 installed, and I've been using it successfully ever since SP1 came out. All of a sudden, any time I have a query with a single line comment (i.e. using dash dash -- ), the rest of the query is ignored as if the single line comment is really a multi-line comment without the closing */

An example:

select top 100 *

from myTable

-- this is a comment

where myTableID = 1234

This would normally return exactly one row, but instead returns 100 rows ( as if the where clause did not exist). If I move the where clause above the comment, it works as expected. Any ideas?

In trying to fix this, I've uninstalled and reinstalled and even reinstalled SP1, but it still isn't fixed.

You've got me stumped. I took the code you have posted and it ran fine for me.

Can you post the exact code that you are using? Maybe we'll see that hanging character you missed or somthing.

|||

I used the exact query, merely changing the table name and ID column.

I ended up going through the process yet again (uninstalling the tools, reinstalling the tools, then installing SP1) and rebooted but still had the problem. However, after a second reboot, it starting behaving properly again. I hope my problem does not resurface.

|||We (me a colleague of mine), have withnessed this same behaviour and, atfer some deep analysis, we have concluded that this bug arises when the Transact-Sql line terminates with a CR (Carriage Return, Ascii(13)) only charaters when it should terminate with both CR (Carriage Return, Ascii(13)) followed by an LF (Line Feed, Ascii(10))

It seems that once SqlServer reachs a single-line comment identifier (--) it keeps fetching bytes untill a compounded line termination (CR followed by LF) is reached.

In the following sample, the {CR+LF} and {CR} are representations of their respective invisible ascii codes.

--This is just a normal single-line comment {CR+LF}
SELECT 'This command works fine' {CR+LF}

--This is a buggy single-line comment {CR}
SELECT 'This command does not work'{CR}
SELECT 'This command does not work either' {CR+LF}
SELECT 'This command work fine too' {CR+LF}

Moreover we have reasons to bellieve that this bug resides in Query Editor provided with SQL Server Management Studio Express Edition (at least, this was version my colleague was using when this bug arose). Anyway, although this bug must be corrected, LF should just be ignored when dealing with Sql scripts.

Running software:

SQL Server Management Studio Express Edition

Ms SQLServer 2000 (8.0.2039)

Win XP Portuguese SP2

Getting this sample you can:

- Load and execute it, using QueryAnalyzer to see the refered behaviour;
- View it, using Notepad, to see what actually happened.