ARODBC Can return odd things if there is no "WHERE" clause.

Even if the "WHERE" clause returns all entries.


On Aug 2, 8:42 am, Jonas Stumph stevnsvig <jo...@stevnsvig.com> wrote:
> Hi again, I'll try not to hit ctrl+enter again... sorry for the triple
> posts.
>
> I am still fiddling with this problem, concering ARODBC and the number
> of records to be returned.
>
> I and querying the incident form on a server with 12000 records, and
> getting very big variations in how many records are being returned. I
> started in excel, and moved to VBscript to
> 1) ascertain whether it was an excel or ARODBC error.
> and
> 2) to be able to correct and experiment faster than waiting for the GUIs in 
> the ODBC system in excel to refresh.
>
> I have tried several different variations of where clauses, as previously 
> suggested (eg. WHERE Incident_Number<>  'ThisOldString') but to no avail.
>
> BMC support is misunderstanding me, and thinks that I am trying on different 
> databases, wih different numbers of records, so I have tried to clarfy my 
> query to them.
>
> Does anyone else have any ideas of what else I can try?
>
> Best regards, Jonas Stevnsvig
>
> ********** SELECT with approximately 60 records returned, of 12000 total
> SELECT
>   *
> FROM
>   HPD_Help_Desk
> ORDER BY
>   Incident_Number DESC
>
> ********** SELECT with approximately 1000 records returned, of 12000 total
> SELECT
>   Incident_Number,
>   Product_Categorization_Tier_1,
>   Product_Categorization_Tier_2,
>   Product_Categorization_Tier_3,
>   First_Name,
>   Last_Name,
>   Site,
>   Status,
>   Priority,
>   Assignee,
>   Assigned_Group,
>   Assignee_Login_ID,
>   Categorization_Tier_1,
>   Categorization_Tier_2,
>   Categorization_Tier_3,
>   Corporate_ID,
>   Reported_Source,
>   Service_Type,
>   Submit_Date,
>   Submitter
> FROM
>   HPD_Help_Desk
> ORDER BY
>   Incident_Number DESC
>
> ********** SELECT with approximately 9500 records returned, of 12000 total
> SELECT
>   Incident_Number,
>   Product_Categorization_Tier_1,
>   Product_Categorization_Tier_2,
>   Product_Categorization_Tier_3,
>   First_Name,
>   Last_Name,
>   Site,
>   Status,
>   Priority,
>   Assignee,
>   Assigned_Group,
>   Assignee_Login_ID,
>   Categorization_Tier_1,
>   Categorization_Tier_2,
>   Categorization_Tier_3,
>   Corporate_ID,
>   Reported_Source,
>   Submit_Date,
>   Submitter
> FROM
>   HPD_Help_Desk
> ORDER BY
>   Incident_Number DESC
>
>   ********** SELECT with 12000 records returned, of 12000 total
> SELECT
>   Incident_Number,
>   Product_Categorization_Tier_1,
>   Product_Categorization_Tier_2,
>   Product_Categorization_Tier_3,
>   First_Name,
>   Last_Name,
>   Site,
>   Status,
>   Priority,
>   Assignee,
>   Assigned_Group,
>   Assignee_Login_ID,
>   Corporate_ID,
>   Reported_Source,
>   Submit_Date,
>   Submitter
> FROM
>   HPD_Help_Desk
> ORDER BY
>   Incident_Number DESC
>
> ___________________________________________________________________________ 
> ____
> UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org
> attend wwrug11www.wwrug.comARSList: "Where the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to