Greetings

My two JOBS which have been in existence for years have disappeared. I do not know what happened to them. The two JOBS are the same except one gets run at 2300 each night and the other one gets run NOW.

I can backup using the command below.

 BACKUP DATABASE es_StockDB AS "esStockDB-Backup-Today"
   TO STORE "ES-StockDB-backups-TEST"
   INCLUDE CATALOG

However, when I try to create a JOB to do the backup using the following command, I receive the error below.

** ElevateDB Error #700 An error was found in the statement at line 8 and column 10 (Expected : but instead found DATABASE)


CREATE JOB "BACKUP-esStockDB-NOW"
RUN AS "Administrator"
FROM DATE '2023-04-23' TO DATE '2023-04-23'
ONCE
BETWEEN TIME '14:08:57.670' AND TIME '14:08:57.670'
CATEGORY ''
BEGIN
 BACKUP DATABASE es_StockDB AS "esStockDB-Backup-Today"
   TO STORE "ES-StockDB-backups-TEST"
   INCLUDE CATALOG
END;

Can someone explain this mystery?


The syntax for backing up the database is below. Why is <BackupName> and <StoreName> delimited by quotes but the DATABASE <name> is not?

BACKUP DATABASE <Name> AS <BackupName>
TO STORE <StoreName>
[DESCRIPTION <Description>]
[INCLUDE CATALOG]

I have seen Ian's recent post with Roy's comments but it despite the similarity, it does not seem to help.


Also, for years EDBManager generates an AV error for some unknown reason. I cannot find a pattern. Sometimes I think it is related to help files but most of the time I have no idea. It can be difficult to get rid of this error. Can someone offer me some clues about this also?

Richard

Richard


Generally, for me, these sort of problems indicate a mismatched quote but I can't spot one. The only thing I can see and I don't know if its significant is the lack of a ; at the end of the statement.

<<The syntax for backing up the database is below. Why is <BackupName> and <StoreName> delimited by quotes but the DATABASE <name> is not?>>

All I can suggest is that you ask Tim and the standards body in that order and be prepared for Tim's answer to be - its the standard!

<<Also, for years EDBManager generates an AV error for some unknown reason. I cannot find a pattern. Sometimes I think it is related to help files but most of the time I have no idea. It can be difficult to get rid of this error. Can someone offer me some clues about this also?>>

What would you say to a user who made that sort of error report? <VBG>

Roy Lambert

Greetings Roy

<< What would you say to a user who made that sort of error report?>>

Um - I do not understand. One of the many things that I do not underatand. It really is not an error report. I am simply asking has anyone else experienced AV errors in Elevate EDB Manager. This has happened for years and once it starts occuring then it is persistent and very inconvenient. I have not reported it because I do not know what to report.

Richard

Richard


OK, next time it happens write down the sequence of things before it happened - all the keystrokes, what databases were open, and sql, scripts or views open. I doubt it will do any good but at least it gives a chance for someone to duplicate the steps and see if it happens to them or provide an idea of where Tim should start looking.

The only other thing I can suggest is that if you have source code to compile EDBManager and run with debugging enabled and something like MadExcept to try and pinpoint the source.

Roy Lambert

Greetings Roy

<<OK, next time it happens write down the sequence of things before it happened - all the keystrokes, what databases were open, and sql, scripts or views open. I doubt it will do any good but at least it gives a chance for someone to duplicate the steps and see if it happens to them or provide an idea of where Tim should start looking.>>


It appears to be processor load related. Sometimes when saving a file or executing a query or procedure, Elevate DB Manager can take a long time to respond. If it does not return and I terminate the process then it will cause the AV when Elevate DB Manager starts up again.

It may be indulgent and tedious but survial takes a lot of time and has to be my first priority. Organising transport, treatment, medications, supplements and government support (plus everything else) takes far too much time. There is still 120 m of fencing that have been damaged by rather extensive flooding that was lapping around the base of our house. Considerable amount of time is taken up by managing registration and subscriptions for my one and only wordpress website. Suppliers are very keen to get your subscription payments but getting support for renewals to keep it viable is a major exercise. Keeping my website operational after I die is high priority.

We live in a regional area where National Broadband Network service is a problem. Children get home from school and have an urgent need to discuss the day’s events and after dinner watching the latest movie before bedtime seems to be a high priority which causes disruption to the service. Even our electricity supply is a problem with power sometimes being unavailable all day.

My one EWB client (Eyre and Smith – remember Snoopy, Charlie and Lucy and the server ServerPC) have been running their Stock DB for over 12 months since the upgrades of their very obsolete Window’s OS. The next important task is upgrading their EWB2 application to EWB3. It is not offering any benefit to the client. Everything is exactly the same except for a minor colour change so the client is aware of that they are now running EWB3.

I thought that re-installing Elevate DB Manager would solve the problem but it does not. I do not know what makes it go away. Sometimes turning the PC off and going to bed seems to help. Turn the machine on in the morning then all is well. I do not know why that would be the case.

Where do I find the notes that documents the issues resolved for each new release?


Richard

Roy,

<<Generally, for me, these sort of problems indicate a mismatched quote but I can't spot one. The only thing I can see and I don't know if its significant is the lack of a ; at the end of the statement.>>

I use Notepad++ which has a great facility for matching delimiters, so I am confident there are no missing quotes or any other delimiters.

The following command works.

BACKUP DATABASE es_StockDB AS "esStockDB-Backup-Today-27Apr2023at1005"
  TO STORE "ES-StockDB-backups-TEST"
  INCLUDE CATALOG

* * * * *

However, the following CREATE JOB does not.. I receive the error below.

** ElevateDB Error #700 An error was found in the statement at line 8 and column 10 (Expected : but instead found DATABASE)


CREATE JOB "BACKUP-esStockDB-NOW"
RUN AS "Administrator"
FROM DATE '2023-04-23' TO DATE '2023-04-23'
ONCE
BETWEEN TIME '14:08:57.670' AND TIME '14:08:57.670'
CATEGORY ''
BEGIN
BACKUP DATABASE es_StockDB AS "esStockDB-Backup-Today"
  TO STORE "ES-StockDB-backups-TEST"
  INCLUDE CATALOG
END;


There was a change a long time ago about how quotes were used to define variables such as "es_StockDB".

I use three toolbars that contain program icons to launch applications. These are docked on the right. This can cause problems with windows being maximised and restored because Windows does not always allow sufficient space for the docked toolbars. I need to delete the toolbars and re-instate them. This seems to be more of a problem with ElevateDB Manager than other applications.

Richard

<<
Richard Harding wrote:

Greetings

My two JOBS which have been in existence for years have disappeared. I do not know what happened to them. The two JOBS are the same except one gets run at 2300 each night and the other one gets run NOW.

I can backup using the command below.

 BACKUP DATABASE es_StockDB AS "esStockDB-Backup-Today"
   TO STORE "ES-StockDB-backups-TEST"
   INCLUDE CATALOG

However, when I try to create a JOB to do the backup using the following command, I receive the error below.

** ElevateDB Error #700 An error was found in the statement at line 8 and column 10 (Expected : but instead found DATABASE)


CREATE JOB "BACKUP-esStockDB-NOW"
RUN AS "Administrator"
FROM DATE '2023-04-23' TO DATE '2023-04-23'
ONCE
BETWEEN TIME '14:08:57.670' AND TIME '14:08:57.670'
CATEGORY ''
BEGIN
 BACKUP DATABASE es_StockDB AS "esStockDB-Backup-Today"
   TO STORE "ES-StockDB-backups-TEST"
   INCLUDE CATALOG
END;

Can someone explain this mystery?

>>

Try this


CREATE JOB "BACKUP-esStockDB-NOW"
RUN AS "Administrator"
FROM DATE '2023-04-23' TO DATE '2023-04-23'
ONCE
BETWEEN TIME '14:08:57.670' AND TIME '14:08:57.670'
CATEGORY ''
BEGIN
 EXECUTE IMMEDIATE ' BACKUP DATABASE "es_StockDB" AS "esStockDB-Backup-Today"
   TO STORE "ES-StockDB-backups-TEST"
   INCLUDE CATALOG';
END;


Raul

Great - thank you Raul. Works well - except for the poor SQL grammar that uses IMMEDIATE as adverb.

<<Try this


CREATE JOB "BACKUP-esStockDB-NOW"
RUN AS "Administrator"
FROM DATE '2023-04-23' TO DATE '2023-04-23'
ONCE
BETWEEN TIME '14:08:57.670' AND TIME '14:08:57.670'
CATEGORY ''
BEGIN
 EXECUTE IMMEDIATE ' BACKUP DATABASE "es_StockDB" AS "esStockDB-Backup-Today"
   TO STORE "ES-StockDB-backups-TEST"
   INCLUDE CATALOG';
END;

>>


Richard

Raul


Well spotted. I just never saw that he was simply trying to run an SQL command without a cursor. I shall now go and stand in the corner with my dunces hat.

Roy Lambert

Roy and Raul

<<I use three toolbars that contain program icons to launch applications. These are docked on the right. This can cause problems with windows being maximised and restored because Windows does not always allow sufficient space for the docked toolbars. I need to delete the toolbars and re-instate them. This seems to be more of a problem with ElevateDB Manager than other applications.>>

Last night I could not power off my machine. <ctl><alt><del> would ldid not give me access to the taks manager. It was difficult to tturn of the machine with the power switch. I tried several times to reboot the PC without success.

Eventuallly powered off the PC, we all went to bed and had a good night's sleep.

This morniing the PC re-booted, did its hard drives disk check and and is now working perfectly well.

Anothor item on my list of things I do not understand.

Thank you both for the big effort.

Richard