Dan,

I have placed a patch version of Guggi on the internet site. Please
download the zip file Guggiexe.zip from

http://www.impact-sol.com/download/Guggiexe.zip

Please unzip the file and save Guggi.exe in the folder where Guggi
for Oracle is installed. The patch version will read 1.5.3 as
version number.

This version of Guggi will resolve the issue with period (".").
Several other cahracters such as " ", ";" ")" , "(" , tab, space, new
line etc. are used to identify word terminators. Please let us know
if you would like other word terminators to be added.


In addition, a modified Reverse Engineer tool has been added that
will allow you to reverse engineer a lot of different type of
objects. Also, you can reverse engineer a select list of objects of
a given type. The tool will reverse advanced objects for Oracle
version 9.2 and higher.

The debugger has also been enhanced to report more error messages,
Run till exception feature has been added. The user can now
also "abort execution" while the debugger is still running.

Thanks

Shakti
http://www.impact-sol.com
Developers of Guggi Oracle - Tool for DBAs and Developers


--- In guggiusers@yahoogroups.com, "Shakti <skgoel@a...>"
<shakti_k_goel@y...> wrote:
>
> Hello Dan,
>
> Thank you for your interest in Guggi Oracle.
>
> We would recommend using Oracle OleDb by Oracle option
> to execute queries. OleDb driver supports most of the
> functionality of Oracle whereas ODBC driver can be
> sometimes limiting.
>
> If you have Oracle client installed then Oledb is
> automatically installed with it, and you would not
> need to take any additional steps.
>
> The issue that you have encountered below is as
> follows:
>
> The tool does not recognize "." as an end-of-word
> character. Therefore, it treats the entire string
>
> &START_DD.&START_MM.2005:00:00:00'
>
> as one parameter.
>
> In order for the script to work, please make the
> following changes
>
> '&START_DD . &START_MM . 2005:00:00:00'
>
> In other words, insert a space before and after the
> period (".")character. The tool will then recognize
> start_dd as a single parameter and same for other
> three parameters.
>
> We have tested this using OleDb driver.
>
> SELECT *
> FROM emp
> WHERE hiredate BETWEEN TO_DATE ('&START_DD .
> &START_MM .1981:00:00:00',
>
> 'DD.MM.YYYY:HH24:MI:SS'
> )
> AND TO_DATE
> ('&END_DD . &END_MM .1981:23:59:59',
> 'DD
> .MM.YYYY:HH24:MI:SS'
> )
>
>
> We will add an option in the tool to recognize "." as
> a character. This option will be placed in the
> Application Options form. You can then turn on-this
> option.
>
> Also, the OleDb and ODBC drivers do not recognize ";"
> as a valid character at the end of SQL statement. We
> are making enhancements to the product to address this
> issue as well.
>
> Hope the response addresses the immediate issue.
> Please let us know if you have any more questions.
>
> Regards,
>
> Shakti
> Sales - Impact Solutions
> http://www.impact-sol.com
> Developers of Guggi Oracle - Tool for DBAs and
> Developers
>
>
> --- Dan <dccorso@y...> wrote:
>
> > Hi,
> >
> > I'm evaluating this product to replace TOAD in our
> > workplace. We
> > are budget cutting :-)
> >
> > We'll need 10 licenses, but while I'm testing
> > scripts that run in
> > TOAD, I get some funky errors in this. I was
> > wondering if some
> > light could be shed on them, and what I need to do
> > to get the
> > scripts to execute properly?
> >
> > Here's what I'm sending:
> > SELECT val1, val2, COUNT(1)
> > FROM table1
> > WHERE ( val3 in ('x1','x2','x3')
> > )
> > AND val4 BETWEEN TO_DATE
> > ('&START_DD.&START_MM.2005:00:00:00',
> >
> > 'DD.MM.YYYY:HH24:MI:SS'
> > )
> > AND TO_DATE
> > ('&END_DD.&END_MM.2005:23:59:59',
> >
> > 'DD.MM.YYYY:HH24:MI:SS'
> > )
> >
> > group by val1, val2;
> >
> > Here's the error that's coming out when I run it as
> > a script:
> >
> > [Oracle][ODBC][Ora]ORA-06550: line 1, column 7:
> > PLS-00103: Encountered the symbol "" when expecting
> > one of the
> > following:
> > begin declare exit for goto if loop mod null
> > pragma raise
> > return select update while <an identifier>
> > <a double-quoted delimited-identifier> <a bind
> > variable> <<
> > close current delete fetch lock insert open
> > rollback
> > savepoint set sql execute commit forall
> > <a single-quoted SQL string>
> > The symbol "" was ignored.
> > ORA-06550: line 12, column 50:
> > PLS-00103: Encountered the sy
> >
> > Now, I know if I were to replace the
> > &START_DD.&START_MM and
> > &END_DD.&END_MM with solid values, it will run fine,
> > but I run these
> > regularly and prefer the prompts. Guggi also seems
> > to not know that
> > I only want to populate those values, as it expects
> > me to include
> > the entire TO_DATE if I just try and execute the
> > statement.
> >
> > Any help would be appreciated. It's a very
> > reasonably priced tool
> > and seems comparable in function to TOAD
> >
> >
> >
> >
> >
>