dbTalk Databases Forums  

ISELECT Limitations (mv.Enterprise)

comp.databases.pick comp.databases.pick


Discuss ISELECT Limitations (mv.Enterprise) in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
morrtech@comcast.net
 
Posts: n/a

Default ISELECT Limitations (mv.Enterprise) - 07-27-2005 , 10:59 AM






Does the ISELECT command (on mv.Enterprise)have limitations in the
number of operands that can be passed to it? I've created the indices
required, but can't seem to make the combination of date ranges,
customer numbers and part numbers execute properly. I receive this
error message:
[23] Invalid sentence: (followed by the command I've entered)

Thanks in advance for any help or advice.

Dave Morrison


Reply With Quote
  #2  
Old   
iakovos@gmail.com
 
Posts: n/a

Default Re: ISELECT Limitations (mv.Enterprise) - 07-27-2005 , 11:35 PM






mve had probs with Indexed files as far as I remember. We tried to use
it once too but found that firstly it wasn't exactly what it was
professing to be, and secondly wasn't all that much faster than the
normal file access mechanisms provided.

I don't know of any limitations to ISELECT but check your syntax again.


Reply With Quote
  #3  
Old   
Ross Ferris
 
Posts: n/a

Default Re: ISELECT Limitations (mv.Enterprise) - 07-28-2005 , 03:30 AM



Could you maybe include that command that it echoes back so people can
at least do a human parse for errors ....


Reply With Quote
  #4  
Old   
morrtech@comcast.net
 
Posts: n/a

Default Re: ISELECT Limitations (mv.Enterprise) - 07-28-2005 , 09:26 AM



Thanks for your response. So far, the 'single' ISELECT command works
significantly faster than a regular SELECT, and matches items selected
perfectly. After some additional testing and analysis of returned
messages, I've made some changes to use ISELECT for the primary 'mass'
select, followed by a series of 'normal' SELECTs to trim the list down
further. mvE ISELECT does have its limitations in this context.

iakovos (AT) gmail (DOT) com wrote:
Quote:
mve had probs with Indexed files as far as I remember. We tried to use
it once too but found that firstly it wasn't exactly what it was
professing to be, and secondly wasn't all that much faster than the
normal file access mechanisms provided.

I don't know of any limitations to ISELECT but check your syntax again.


Reply With Quote
  #5  
Old   
morrtech@comcast.net
 
Posts: n/a

Default Re: ISELECT Limitations (mv.Enterprise) - 07-28-2005 , 09:36 AM



Ross,

Thanks for your response. That is exactly what I did and realized
ISELECT works well on the first shot, but abandons the initial list
upon any subsequent ISELECT commands. So I've just included some normal
SELECT commands following to trim down the list. It still out performs
a normal select by a long shot.

Dave


Reply With Quote
Reply




Thread Tools
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

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.