How can we help you today? How can we help you today?
Tilman
Hi, Thanks for the feedback. We'll try and incorporate it into a future version. Regards, Tilman / comments
Hi, Thanks for the feedback. We'll try and incorporate it into a future version. Regards, Tilman
0 votes
Hi I also posted this same suggestion on this thread. Please see my response to that thread. Tilman / comments
Hi I also posted this same suggestion on this thread. Please see my response to that thread. Tilman
0 votes
Yes, I would suggest at least putting a '*' there, don't leave it empty. The more valid your SQL is, the better Prompt will work. Tilman / comments
Yes, I would suggest at least putting a '*' there, don't leave it empty. The more valid your SQL is, the better Prompt will work. Tilman
0 votes
Hi, have you tried switching off '.' as a completion key? You can do this on the Candidates tab of the Options dialog. Regards, Tilman / comments
Hi, have you tried switching off '.' as a completion key? You can do this on the Candidates tab of the Options dialog. Regards, Tilman
0 votes
Hi, PostPosted: Thu Dec 14, 2006 5:10 pm Post subject: Re: tgoldstein@co.arapahoe wrote: All in all I think this functionality has gone from almost right to more work than it is worth. I'm trying to stick with it but it does seem to hinder me more at times then help. Other people have also mentioned this and I have added it to our list to bring back the v2 functionality. However, I don't think it will happen vor v3.0, though. Hitting comma at the end of a field causes a candidate list to appear. Probably a good thing since it is expecting you to select the next field. Instead, I want to hit enter to put the field on a new line. So I get the first item in the candidate list instead. We will make the Enter key configurable in the final release, so you can turn it off as a completion key. For now, you could turn up auto-pop up all thogether. Otherwise, Esc is your friend [image] If you expand the wildcard character '*' or use the column picker you can specify to insert each column on a new line. Arrowing up and down in a 1300+ line stored procedure is a lot slower. Paging up and down has no performance hit. We are aware of the issue and hope to improve it for the final release. Copying a section of code (regardless of size) causes a 3-5 second pause. I'm afraid I can't reproduce this. Could you tell me what editor you are using? Regards, Tilman / comments
Hi, PostPosted: Thu Dec 14, 2006 5:10 pm Post subject: Re:tgoldstein@co.arapahoe wrote: All in all I think this functionality has gone from almost right to more work than it is worth. I'm tryin...
0 votes