How to use SQL "LIMIT" keyword against an MDB file

This is a discussion on How to use SQL "LIMIT" keyword against an MDB file within the PHP Language forums, part of the PHP Programming Forums category; "NC" <nc@iname.com> wrote in message news:093fa743-0beb-4582-b9e2-8baaf8531f0b@s37g2000prg.googlegroups.com... &...


Go Back   Usenet Forums > PHP Programming Forums > PHP Language

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #21 (permalink)  
Old 01-30-2008
Steve
 
Posts: n/a
Default Re: How to use SQL "LIMIT" keyword against an MDB file


"NC" <nc@iname.com> wrote in message
news:093fa743-0beb-4582-b9e2-8baaf8531f0b@s37g2000prg.googlegroups.com...
> On Jan 28, 1:37 pm, Martin <martinval...@comcast.net> wrote:
>>
>> I'm trying to adapt a PHP script that was written to use MySQL,
>> so that it will work with an MSAccess MDB file.

>
> Good luck...
>
>> An important part of the script makes use of the SQL "LIMIT"
>> keyword available in MySQL. eg: "SELECT MyField FROM MyTable
>> LIMIT 40,10" to select 10 records beginning at the 41st record.
>>
>> Can anyone tell me how I can achieve this same functionality
>> when using ODBC functions to access an MDB file?

>
> You can't. Access does not support LIMIT clauses.


BULLSHIT !!!

*acheive ... functionality*...the two key words. i've given an explanation
of at least one way...which falsifies your claim, btw.

> The closet thing you can do is to run this query:
>
> SELECT TOP 50 MyField FROM MyTable


BULLSHIT !!!

> and then loop through first 40 records returned without doing
> anything and start your processing from the 41st record.


more lunacy.


Reply With Quote
  #22 (permalink)  
Old 01-30-2008
Ivan Marsh
 
Posts: n/a
Default Re: How to use SQL "LIMIT" keyword against an MDB file

On Wed, 30 Jan 2008 11:34:57 -0600, Steve wrote:


> "NC" <nc@iname.com> wrote in message
> news:093fa743-0beb-4582-b9e2-8baaf8531f0b@s37g2000prg.googlegroups.com...
>> On Jan 28, 1:37 pm, Martin <martinval...@comcast.net> wrote:
>>>
>>> I'm trying to adapt a PHP script that was written to use MySQL, so
>>> that it will work with an MSAccess MDB file.

>>
>> Good luck...
>>
>>> An important part of the script makes use of the SQL "LIMIT" keyword
>>> available in MySQL. eg: "SELECT MyField FROM MyTable LIMIT 40,10" to
>>> select 10 records beginning at the 41st record.
>>>
>>> Can anyone tell me how I can achieve this same functionality when
>>> using ODBC functions to access an MDB file?

>>
>> You can't. Access does not support LIMIT clauses.

>
> BULLSHIT !!!
>
> *acheive ... functionality*...the two key words. i've given an
> explanation of at least one way...which falsifies your claim, btw.


No... you have not.

--
I told you this was going to happen.

Reply With Quote
  #23 (permalink)  
Old 01-30-2008
Steve
 
Posts: n/a
Default Re: How to use SQL "LIMIT" keyword against an MDB file


"Ivan Marsh" <annoyed@you.now> wrote in message
news:pan.2008.01.30.17.44.49.792094@you.now...
> On Wed, 30 Jan 2008 11:34:57 -0600, Steve wrote:
>
>
>> "NC" <nc@iname.com> wrote in message
>> news:093fa743-0beb-4582-b9e2-8baaf8531f0b@s37g2000prg.googlegroups.com...
>>> On Jan 28, 1:37 pm, Martin <martinval...@comcast.net> wrote:
>>>>
>>>> I'm trying to adapt a PHP script that was written to use MySQL, so
>>>> that it will work with an MSAccess MDB file.
>>>
>>> Good luck...
>>>
>>>> An important part of the script makes use of the SQL "LIMIT" keyword
>>>> available in MySQL. eg: "SELECT MyField FROM MyTable LIMIT 40,10" to
>>>> select 10 records beginning at the 41st record.
>>>>
>>>> Can anyone tell me how I can achieve this same functionality when
>>>> using ODBC functions to access an MDB file?
>>>
>>> You can't. Access does not support LIMIT clauses.

>>
>> BULLSHIT !!!
>>
>> *acheive ... functionality*...the two key words. i've given an
>> explanation of at least one way...which falsifies your claim, btw.

>
> No... you have not.


christ almighty!!!

<quote>
the easiest way is to select into a temp table where one of the columns is
an auto-number...the query then becomes WHERE blah BETWEEN x AND n
</quote>

do you need the message id too?

but while i'm at it:

===========

create table companies
(
company NUMBER ,
name TEXT ,
region NUMBER
)

SELECT *
FROM
(
SELECT (
SELECT COUNT(*)
FROM companies AS r
WHERE r.Company < co.Company
) AS RowNum ,
co.Company AS Company ,
co.Name AS Name ,
co.Region AS Region
FROM companies AS co
)
WHERE RowNum BETWEEN 50 AND 100
ORDER BY RowNum

===========

fuck you very much.

oh, that would be explanation #2...demonstrated specifically for ms access.


Reply With Quote
  #24 (permalink)  
Old 01-30-2008
Ivan Marsh
 
Posts: n/a
Default Re: How to use SQL "LIMIT" keyword against an MDB file

On Wed, 30 Jan 2008 14:10:02 -0600, Steve wrote:


> "Ivan Marsh" <annoyed@you.now> wrote in message
> news:pan.2008.01.30.17.44.49.792094@you.now...
>> On Wed, 30 Jan 2008 11:34:57 -0600, Steve wrote:
>>
>>
>>> "NC" <nc@iname.com> wrote in message
>>> news:093fa743-0beb-4582-b9e2-8baaf8531f0b@s37g2000prg.googlegroups.com...
>>>> On Jan 28, 1:37 pm, Martin <martinval...@comcast.net> wrote:
>>>>>
>>>>> I'm trying to adapt a PHP script that was written to use MySQL, so
>>>>> that it will work with an MSAccess MDB file.
>>>>
>>>> Good luck...
>>>>
>>>>> An important part of the script makes use of the SQL "LIMIT" keyword
>>>>> available in MySQL. eg: "SELECT MyField FROM MyTable LIMIT 40,10" to
>>>>> select 10 records beginning at the 41st record.
>>>>>
>>>>> Can anyone tell me how I can achieve this same functionality when
>>>>> using ODBC functions to access an MDB file?
>>>>
>>>> You can't. Access does not support LIMIT clauses.
>>>
>>> BULLSHIT !!!
>>>
>>> *acheive ... functionality*...the two key words. i've given an
>>> explanation of at least one way...which falsifies your claim, btw.

>>
>> No... you have not.

>
> christ almighty!!!
>
> <quote>
> the easiest way is to select into a temp table where one of the columns
> is an auto-number...the query then becomes WHERE blah BETWEEN x AND n
> </quote>
>
> do you need the message id too?
>
> but while i'm at it:
>
> ===========
>
> create table companies
> (
> company NUMBER ,
> name TEXT ,
> region NUMBER
> )
>
> SELECT *
> FROM
> (
> SELECT (
> SELECT COUNT(*)
> FROM companies AS r
> WHERE r.Company < co.Company
> ) AS RowNum ,
> co.Company AS Company ,
> co.Name AS Name ,
> co.Region AS Region
> FROM companies AS co
> )
> WHERE RowNum BETWEEN 50 AND 100 ORDER BY RowNum


....and have you verified that any of this works with PHP/ODBC hitting a
MDB file?

> fuck you very much.


I'm sorry you have a tiny dick but if you can't be civil you can kiss my
ass you two year old pansy.

--
I told you this was going to happen.

Reply With Quote
  #25 (permalink)  
Old 01-30-2008
Paul Lautman
 
Posts: n/a
Default Re: How to use SQL "LIMIT" keyword against an MDB file

Ivan Marsh wrote:
> On Wed, 30 Jan 2008 14:10:02 -0600, Steve wrote:
>>
>> SELECT *
>> FROM
>> (
>> SELECT (
>> SELECT COUNT(*)
>> FROM companies AS r
>> WHERE r.Company < co.Company
>> ) AS RowNum ,
>> co.Company AS Company ,
>> co.Name AS Name ,
>> co.Region AS Region
>> FROM companies AS co
>> )
>> WHERE RowNum BETWEEN 50 AND 100 ORDER BY RowNum

>
> ...and have you verified that any of this works with PHP/ODBC hitting
> a MDB file?

He may not have bothered since he doesn't actually want to do it himself.
However, since it is indeed Microsoft's advice of how to do it, they may
well have.


Reply With Quote
  #26 (permalink)  
Old 01-31-2008
Steve
 
Posts: n/a
Default Re: How to use SQL "LIMIT" keyword against an MDB file


"Ivan Marsh" <annoyed@you.now> wrote in message
news:pan.2008.01.30.22.27.46.903923@you.now...
> On Wed, 30 Jan 2008 14:10:02 -0600, Steve wrote:
>
>
>> "Ivan Marsh" <annoyed@you.now> wrote in message
>> news:pan.2008.01.30.17.44.49.792094@you.now...
>>> On Wed, 30 Jan 2008 11:34:57 -0600, Steve wrote:
>>>
>>>
>>>> "NC" <nc@iname.com> wrote in message
>>>> news:093fa743-0beb-4582-b9e2-8baaf8531f0b@s37g2000prg.googlegroups.com...
>>>>> On Jan 28, 1:37 pm, Martin <martinval...@comcast.net> wrote:
>>>>>>
>>>>>> I'm trying to adapt a PHP script that was written to use MySQL, so
>>>>>> that it will work with an MSAccess MDB file.
>>>>>
>>>>> Good luck...
>>>>>
>>>>>> An important part of the script makes use of the SQL "LIMIT" keyword
>>>>>> available in MySQL. eg: "SELECT MyField FROM MyTable LIMIT 40,10" to
>>>>>> select 10 records beginning at the 41st record.
>>>>>>
>>>>>> Can anyone tell me how I can achieve this same functionality when
>>>>>> using ODBC functions to access an MDB file?
>>>>>
>>>>> You can't. Access does not support LIMIT clauses.
>>>>
>>>> BULLSHIT !!!
>>>>
>>>> *acheive ... functionality*...the two key words. i've given an
>>>> explanation of at least one way...which falsifies your claim, btw.
>>>
>>> No... you have not.

>>
>> christ almighty!!!
>>
>> <quote>
>> the easiest way is to select into a temp table where one of the columns
>> is an auto-number...the query then becomes WHERE blah BETWEEN x AND n
>> </quote>
>>
>> do you need the message id too?
>>
>> but while i'm at it:
>>
>> ===========
>>
>> create table companies
>> (
>> company NUMBER ,
>> name TEXT ,
>> region NUMBER
>> )
>>
>> SELECT *
>> FROM
>> (
>> SELECT (
>> SELECT COUNT(*)
>> FROM companies AS r
>> WHERE r.Company < co.Company
>> ) AS RowNum ,
>> co.Company AS Company ,
>> co.Name AS Name ,
>> co.Region AS Region
>> FROM companies AS co
>> )
>> WHERE RowNum BETWEEN 50 AND 100 ORDER BY RowNum

>
> ...and have you verified that any of this works with PHP/ODBC hitting a
> MDB file?


uhmmm, that's the funny thing about odbc...it DOESN'T have a thing to do
with queries! it is a communacative pass-thru between a caller and a db
resource. but yes, i tested it. works just fine.

>> fuck you very much.

>
> I'm sorry you have a tiny dick but if you can't be civil you can kiss my
> ass you two year old pansy.


hey, if you didn't make stupid suggestions...check that...insane suggestions
and then demonstrate that you can't read, maybe my response would be less
frank. you notice that in my second response to you, i backed off quite a
bit (almost civil in tone :) when i thought i'd just mis-understood you.
nope, you just kept forging ahead.

and, who uses the word 'pansy' anymore? sad though, that this two year old
pansy has to set your saged knoggin right.


Reply With Quote
  #27 (permalink)  
Old 01-31-2008
Steve
 
Posts: n/a
Default Re: How to use SQL "LIMIT" keyword against an MDB file


"Paul Lautman" <paul.lautman@btinternet.com> wrote in message
news:60ccruF1pqpbuU1@mid.individual.net...
> Ivan Marsh wrote:
>> On Wed, 30 Jan 2008 14:10:02 -0600, Steve wrote:
>>>
>>> SELECT *
>>> FROM
>>> (
>>> SELECT (
>>> SELECT COUNT(*)
>>> FROM companies AS r
>>> WHERE r.Company < co.Company
>>> ) AS RowNum ,
>>> co.Company AS Company ,
>>> co.Name AS Name ,
>>> co.Region AS Region
>>> FROM companies AS co
>>> )
>>> WHERE RowNum BETWEEN 50 AND 100 ORDER BY RowNum

>>
>> ...and have you verified that any of this works with PHP/ODBC hitting
>> a MDB file?

> He may not have bothered since he doesn't actually want to do it himself.
> However, since it is indeed Microsoft's advice of how to do it, they may
> well have.


usually when someone gets persistent with wanting more than theory or copy,
i work out the details and actually test it before i post it here. the only
time i don't test is when i specifically say "this should work, but i
haven't tested it".

as for microsoft's suggestion, i'm sure they would give such advice. though
the above is fully functional, it causes much overhead and doesn't scale
well. the better suggestion, though i didn't demo it here, is to create a
temp table with an additional, autonumbered field. that field would equate
to ROWNUM after inserting your SELECTed data...inclusive of condition
clauses and ordering. but, ms isn't always the best discriminator of
efficiency and effectiveness.

cheers.


Reply With Quote
  #28 (permalink)  
Old 01-31-2008
Ivan Marsh
 
Posts: n/a
Default Re: How to use SQL "LIMIT" keyword against an MDB file

On Wed, 30 Jan 2008 23:41:29 -0600, Steve wrote:

> "Ivan Marsh" <annoyed@you.now> wrote in message
> news:pan.2008.01.30.22.27.46.903923@you.now...
>> On Wed, 30 Jan 2008 14:10:02 -0600, Steve wrote:
>>> "Ivan Marsh" <annoyed@you.now> wrote in message
>>> news:pan.2008.01.30.17.44.49.792094@you.now...
>>>> On Wed, 30 Jan 2008 11:34:57 -0600, Steve wrote:
>>>>> "NC" <nc@iname.com> wrote in message
>>>>> news:093fa743-0beb-4582-b9e2-8baaf8531f0b@s37g2000prg.googlegroups.com...
>>>>>> On Jan 28, 1:37 pm, Martin <martinval...@comcast.net> wrote:
>>>>>>>
>>>>>>> I'm trying to adapt a PHP script that was written to use MySQL, so
>>>>>>> that it will work with an MSAccess MDB file.
>>>>>>
>>>>>> Good luck...
>>>>>>
>>>>>>> An important part of the script makes use of the SQL "LIMIT" keyword
>>>>>>> available in MySQL. eg: "SELECT MyField FROM MyTable LIMIT 40,10" to
>>>>>>> select 10 records beginning at the 41st record.
>>>>>>>
>>>>>>> Can anyone tell me how I can achieve this same functionality when
>>>>>>> using ODBC functions to access an MDB file?
>>>>>>
>>>>>> You can't. Access does not support LIMIT clauses.
>>>>>
>>>>> BULLSHIT !!!
>>>>>
>>>>> *acheive ... functionality*...the two key words. i've given an
>>>>> explanation of at least one way...which falsifies your claim, btw.
>>>>
>>>> No... you have not.
>>>
>>> christ almighty!!!
>>>
>>> <quote>
>>> the easiest way is to select into a temp table where one of the columns
>>> is an auto-number...the query then becomes WHERE blah BETWEEN x AND n
>>> </quote>
>>>
>>> do you need the message id too?
>>>
>>> but while i'm at it:
>>>
>>> ===========
>>>
>>> create table companies
>>> (
>>> company NUMBER ,
>>> name TEXT ,
>>> region NUMBER
>>> )
>>>
>>> SELECT *
>>> FROM
>>> (
>>> SELECT (
>>> SELECT COUNT(*)
>>> FROM companies AS r
>>> WHERE r.Company < co.Company
>>> ) AS RowNum ,
>>> co.Company AS Company ,
>>> co.Name AS Name ,
>>> co.Region AS Region
>>> FROM companies AS co
>>> )
>>> WHERE RowNum BETWEEN 50 AND 100 ORDER BY RowNum

>>
>> ...and have you verified that any of this works with PHP/ODBC hitting a
>> MDB file?

>
> uhmmm, that's the funny thing about odbc...it DOESN'T have a thing to do
> with queries! it is a communacative pass-thru between a caller and a db
> resource. but yes, i tested it. works just fine.


That's all I ask for. Your first two examples didn't work so it wouldn't
be too smart to blindly trust a third. It's funny that something you
professed to be so easy took you three attempts.

>>> fuck you very much.

>>
>> I'm sorry you have a tiny dick but if you can't be civil you can kiss my
>> ass you two year old pansy.

>
> hey, if you didn't make stupid suggestions...check that...insane suggestions
> and then demonstrate that you can't read, maybe my response would be less
> frank. you notice that in my second response to you, i backed off quite a
> bit (almost civil in tone :) when i thought i'd just mis-understood you.
> nope, you just kept forging ahead.


Why don't you try just not being an arrogant asshole in the first place?

> and, who uses the word 'pansy' anymore? sad though, that this two year
> old pansy has to set your saged knoggin right.


What's sad is that you think you have to be a dick to get your point
across. Rater than offering useful suggestions you go straight to being an
arrogant, insulting piece of crap and then it still takes you three tries
to get the code right... sort of proves my point that you don't have the
same functionality as you would with an SQL server doesn't it?

--
I told you this was going to happen.

Reply With Quote
  #29 (permalink)  
Old 01-31-2008
Steve
 
Posts: n/a
Default Re: How to use SQL "LIMIT" keyword against an MDB file


"Ivan Marsh" <annoyed@you.now> wrote in message
news:pan.2008.01.31.17.02.03.361056@you.now...
> On Wed, 30 Jan 2008 23:41:29 -0600, Steve wrote:
>
>> "Ivan Marsh" <annoyed@you.now> wrote in message
>> news:pan.2008.01.30.22.27.46.903923@you.now...
>>> On Wed, 30 Jan 2008 14:10:02 -0600, Steve wrote:
>>>> "Ivan Marsh" <annoyed@you.now> wrote in message
>>>> news:pan.2008.01.30.17.44.49.792094@you.now...
>>>>> On Wed, 30 Jan 2008 11:34:57 -0600, Steve wrote:
>>>>>> "NC" <nc@iname.com> wrote in message
>>>>>> news:093fa743-0beb-4582-b9e2-8baaf8531f0b@s37g2000prg.googlegroups.com...
>>>>>>> On Jan 28, 1:37 pm, Martin <martinval...@comcast.net> wrote:
>>>>>>>>
>>>>>>>> I'm trying to adapt a PHP script that was written to use MySQL, so
>>>>>>>> that it will work with an MSAccess MDB file.
>>>>>>>
>>>>>>> Good luck...
>>>>>>>
>>>>>>>> An important part of the script makes use of the SQL "LIMIT"
>>>>>>>> keyword
>>>>>>>> available in MySQL. eg: "SELECT MyField FROM MyTable LIMIT 40,10"
>>>>>>>> to
>>>>>>>> select 10 records beginning at the 41st record.
>>>>>>>>
>>>>>>>> Can anyone tell me how I can achieve this same functionality when
>>>>>>>> using ODBC functions to access an MDB file?
>>>>>>>
>>>>>>> You can't. Access does not support LIMIT clauses.
>>>>>>
>>>>>> BULLSHIT !!!
>>>>>>
>>>>>> *acheive ... functionality*...the two key words. i've given an
>>>>>> explanation of at least one way...which falsifies your claim, btw.
>>>>>
>>>>> No... you have not.
>>>>
>>>> christ almighty!!!
>>>>
>>>> <quote>
>>>> the easiest way is to select into a temp table where one of the columns
>>>> is an auto-number...the query then becomes WHERE blah BETWEEN x AND n
>>>> </quote>
>>>>
>>>> do you need the message id too?
>>>>
>>>> but while i'm at it:
>>>>
>>>> ===========
>>>>
>>>> create table companies
>>>> (
>>>> company NUMBER ,
>>>> name TEXT ,
>>>> region NUMBER
>>>> )
>>>>
>>>> SELECT *
>>>> FROM
>>>> (
>>>> SELECT (
>>>> SELECT COUNT(*)
>>>> FROM companies AS r
>>>> WHERE r.Company < co.Company
>>>> ) AS RowNum ,
>>>> co.Company AS Company ,
>>>> co.Name AS Name ,
>>>> co.Region AS Region
>>>> FROM companies AS co
>>>> )
>>>> WHERE RowNum BETWEEN 50 AND 100 ORDER BY RowNum
>>>
>>> ...and have you verified that any of this works with PHP/ODBC hitting a
>>> MDB file?

>>
>> uhmmm, that's the funny thing about odbc...it DOESN'T have a thing to do
>> with queries! it is a communacative pass-thru between a caller and a db
>> resource. but yes, i tested it. works just fine.

>
> That's all I ask for. Your first two examples didn't work so it wouldn't
> be too smart to blindly trust a third. It's funny that something you
> professed to be so easy took you three attempts.


good god, dumbass! the first suggestion works, i just didn't spell it out
with actual code. the one i showed here is the access version of the oracle
example - the second example i talked about. and, guess what? the oracle
example works fine in oracle. funny that.

every suggestion i made works. sorry if you can't read and engineer. are you
wanting a macro example too, because i said that was a third option.

again, fuck you very much.

>>>> fuck you very much.
>>>
>>> I'm sorry you have a tiny dick but if you can't be civil you can kiss my
>>> ass you two year old pansy.

>>
>> hey, if you didn't make stupid suggestions...check that...insane
>> suggestions
>> and then demonstrate that you can't read, maybe my response would be less
>> frank. you notice that in my second response to you, i backed off quite a
>> bit (almost civil in tone :) when i thought i'd just mis-understood you.
>> nope, you just kept forging ahead.

>
> Why don't you try just not being an arrogant asshole in the first place?


not arrogant, just can't stand blatant stupidity.

>> and, who uses the word 'pansy' anymore? sad though, that this two year
>> old pansy has to set your saged knoggin right.

>
> What's sad is that you think you have to be a dick to get your point
> across. Rater than offering useful suggestions you go straight to being an
> arrogant, insulting piece of crap and then it still takes you three tries
> to get the code right... sort of proves my point that you don't have the
> same functionality as you would with an SQL server doesn't it?


i don't 'think' i have to act any kind of way.

what does 'rater' mean anyway?

every suggestion i made was useful. further, i never made a comparison
between sql server, mysql, and access. i simply said LIMIT being absent from
access doesn't mean you can't get the functionality thereof...and in less
idiotic ways that you suggested. and to be clear, i gave but two pieces of
code. both work, but both are for specific db's. sorry you're an idiot. at
least i have to 'act' like a dick. you can't escape your double-digit iq,
however.


Reply With Quote
  #30 (permalink)  
Old 01-31-2008
Ivan Marsh
 
Posts: n/a
Default Re: How to use SQL "LIMIT" keyword against an MDB file

On Thu, 31 Jan 2008 11:22:37 -0600, Steve wrote:


> "Ivan Marsh" <annoyed@you.now> wrote in message
> news:pan.2008.01.31.17.02.03.361056@you.now...
>> On Wed, 30 Jan 2008 23:41:29 -0600, Steve wrote:
>>
>>> "Ivan Marsh" <annoyed@you.now> wrote in message
>>> news:pan.2008.01.30.22.27.46.903923@you.now...
>>>> On Wed, 30 Jan 2008 14:10:02 -0600, Steve wrote:
>>>>> "Ivan Marsh" <annoyed@you.now> wrote in message
>>>>> news:pan.2008.01.30.17.44.49.792094@you.now...
>>>>>> On Wed, 30 Jan 2008 11:34:57 -0600, Steve wrote:
>>>>>>> "NC" <nc@iname.com> wrote in message
>>>>>>> news:093fa743-0beb-4582-b9e2-8baaf8531f0b@s37g2000prg.googlegroups.com...
>>>>>>>> On Jan 28, 1:37 pm, Martin <martinval...@comcast.net> wrote:
>>>>>>>>>
>>>>>>>>> I'm trying to adapt a PHP script that was written to use MySQL,
>>>>>>>>> so that it will work with an MSAccess MDB file.
>>>>>>>>
>>>>>>>> Good luck...
>>>>>>>>
>>>>>>>>> An important part of the script makes use of the SQL "LIMIT"
>>>>>>>>> keyword
>>>>>>>>> available in MySQL. eg: "SELECT MyField FROM MyTable LIMIT
>>>>>>>>> 40,10" to
>>>>>>>>> select 10 records beginning at the 41st record.
>>>>>>>>>
>>>>>>>>> Can anyone tell me how I can achieve this same functionality
>>>>>>>>> when using ODBC functions to access an MDB file?
>>>>>>>>
>>>>>>>> You can't. Access does not support LIMIT clauses.
>>>>>>>
>>>>>>> BULLSHIT !!!
>>>>>>>
>>>>>>> *acheive ... functionality*...the two key words. i've given an
>>>>>>> explanation of at least one way...which falsifies your claim, btw.
>>>>>>
>>>>>> No... you have not.
>>>>>
>>>>> christ almighty!!!
>>>>>
>>>>> <quote>
>>>>> the easiest way is to select into a temp table where one of the
>>>>> columns is an auto-number...the query then becomes WHERE blah
>>>>> BETWEEN x AND n </quote>
>>>>>
>>>>> do you need the message id too?
>>>>>
>>>>> but while i'm at it:
>>>>>
>>>>> ===========
>>>>>
>>>>> create table companies
>>>>> (
>>>>> company NUMBER ,
>>>>> name TEXT ,
>>>>> region NUMBER
>>>>> )
>>>>>
>>>>> SELECT *
>>>>> FROM
>>>>> (
>>>>> SELECT (
>>>>> SELECT COUNT(*)
>>>>> FROM companies AS r
>>>>> WHERE r.Company < co.Company
>>>>> ) AS RowNum ,
>>>>> co.Company AS Company ,
>>>>> co.Name AS Name ,
>>>>> co.Region AS Region
>>>>> FROM companies AS co
>>>>> )
>>>>> WHERE RowNum BETWEEN 50 AND 100 ORDER BY RowNum
>>>>
>>>> ...and have you verified that any of this works with PHP/ODBC hitting
>>>> a MDB file?
>>>
>>> uhmmm, that's the funny thing about odbc...it DOESN'T have a thing to
>>> do with queries! it is a communacative pass-thru between a caller and
>>> a db resource. but yes, i tested it. works just fine.

>>
>> That's all I ask for. Your first two examples didn't work so it
>> wouldn't be too smart to blindly trust a third. It's funny that
>> something you professed to be so easy took you three attempts.

>
> good god, dumbass! the first suggestion works, i just didn't spell it
> out with actual code. the one i showed here is the access version of the
> oracle example - the second example i talked about. and, guess what? the
> oracle example works fine in oracle. funny that.
>
> every suggestion i made works. sorry if you can't read and engineer. are
> you wanting a macro example too, because i said that was a third option.
>
> again, fuck you very much.
>
>>>>> fuck you very much.
>>>>
>>>> I'm sorry you have a tiny dick but if you can't be civil you can kiss
>>>> my ass you two year old pansy.
>>>
>>> hey, if you didn't make stupid suggestions...check that...insane
>>> suggestions
>>> and then demonstrate that you can't read, maybe my response would be
>>> less frank. you notice that in my second response to you, i backed off
>>> quite a bit (almost civil in tone :) when i thought i'd just
>>> mis-understood you. nope, you just kept forging ahead.

>>
>> Why don't you try just not being an arrogant asshole in the first
>> place?

>
> not arrogant, just can't stand blatant stupidity.
>
>>> and, who uses the word 'pansy' anymore? sad though, that this two year
>>> old pansy has to set your saged knoggin right.

>>
>> What's sad is that you think you have to be a dick to get your point
>> across. Rater than offering useful suggestions you go straight to being
>> an arrogant, insulting piece of crap and then it still takes you three
>> tries to get the code right... sort of proves my point that you don't
>> have the same functionality as you would with an SQL server doesn't it?

>
> i don't 'think' i have to act any kind of way.
>
> what does 'rater' mean anyway?


It's a simple misspelling of "rather"... what does "communacative" mean?

> every suggestion i made was useful. further, i never made a comparison
> between sql server, mysql, and access. i simply said LIMIT being absent
> from access doesn't mean you can't get the functionality thereof...and
> in less idiotic ways that you suggested. and to be clear, i gave but two
> pieces of code. both work, but both are for specific db's. sorry you're
> an idiot. at least i have to 'act' like a dick. you can't escape your
> double-digit iq, however.


Once again, proving my point.

All hail Steve the Infallible... you an Thomas should date.

--
I told you this was going to happen.

Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT +1. The time now is 10:03 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0