Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 9 of 9 total |
EDB Mgr A/V |
Fri, Oct 10 2008 10:18 AM | Permanent Link |
"David Cornelius" | If I use EDB Manager 2.01 b5 to create a table using the GUI (not SQL),
I can repeatedly generate an Access Violation by taking the following steps: 1. Type in the name in the General Tab 2. Switch to the Columns tab and add a column 3. Switch back to the General tab 4. Change the table name and click OK. -- David Cornelius CorneliusConcepts.com |
Fri, Oct 10 2008 2:03 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | David,
<< If I use EDB Manager 2.01 b5 to create a table using the GUI (not SQL), I can repeatedly generate an Access Violation by taking the following steps: >> I'm not seeing it with the 2.02 candidate EDB Manager, so it must have been fixed as part of some other changes (there are a ton of changes/fixes in 2.02 for the EDB Manager). -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Oct 10 2008 2:49 PM | Permanent Link |
"David Cornelius" | > I'm not seeing it with the 2.02 candidate EDB Manager, so it must
> have been fixed as part of some other changes (there are a ton of > changes/fixes in 2.02 for the EDB Manager). I hope so. Thanks for the note. -- David Cornelius CorneliusConcepts.com |
Tue, Oct 14 2008 3:23 AM | Permanent Link |
"David Cornelius" | > > I'm not seeing it with the 2.02 candidate EDB Manager, so it must
> > have been fixed as part of some other changes (there are a ton of > > changes/fixes in 2.02 for the EDB Manager). > > I hope so. Thanks for the note. Unfortuneately, 2.02 is worse. There are A/Vs and Index out of Bounds and meta table corruption and more. I have to move back to 2.01 b5 for now. I submitted two incident reports, but will have to wait until any other bugs are shaken out and fixed before moving up. -- David Cornelius CorneliusConcepts.com |
Tue, Oct 14 2008 10:51 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | David,
<< Unfortuneately, 2.02 is worse. There are A/Vs and Index out of Bounds and meta table corruption and more. I have to move back to 2.01 b5 for now. I submitted two incident reports, but will have to wait until any other bugs are shaken out and fixed before moving up. >> BTW, apart from the meta-data issue with publishing tables and then altering them (which I have *not* confirmed yet and is already in our test framework), we have only one issue that I'm aware of in the EDB Manager. And that does *not* affect the engine itself. Is there any reason that you're running all of this in the EDB Manager and not in an actual application ? IOW, there's no reason to run scripts in the EDB Manager debugger if you're running them in a production environment. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Oct 14 2008 10:53 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | David,
<< Unfortuneately, 2.02 is worse. There are A/Vs and Index out of Bounds and meta table corruption and more. I have to move back to 2.01 b5 for now. I submitted two incident reports, but will have to wait until any other bugs are shaken out and fixed before moving up. >> Neither of those two incident reports mention an "index out of bounds" or AV error. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Oct 14 2008 11:09 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | David,
<< Neither of those two incident reports mention an "index out of bounds" or AV error. >> Scratch that - I missed where you mentioned this in relation to the log messages issue. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Oct 14 2008 12:14 PM | Permanent Link |
"David Cornelius" | > BTW, apart from the meta-data issue with publishing tables and then
> altering them (which I have not confirmed yet and is already in our > test framework), we have only one issue that I'm aware of in the EDB > Manager. And that does not affect the engine itself. Is there any > reason that you're running all of this in the EDB Manager and not in > an actual application ? IOW, there's no reason to run scripts in the > EDB Manager debugger if you're running them in a production > environment. I have a lot of scripts in the application. They seem to be doing fine. The stuff I'm doing in EDB Manager is configuration, or testing or small queries to find out why something is happening. The customer's application is still in a state of flux and sometimes I need to fix things manually. Nothing I do in EDB Manager is automated--or if it is, I'm still testing it before putting into a job or the application. -- David Cornelius CorneliusConcepts.com |
Tue, Oct 14 2008 12:45 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | David,
<< I have a lot of scripts in the application. They seem to be doing fine. >> Good, they should be. All of these issues are specific to the EDB Manager, and more specifically, confined to the script debugging. << The stuff I'm doing in EDB Manager is configuration, or testing or small queries to find out why something is happening. The customer's application is still in a state of flux and sometimes I need to fix things manually. Nothing I do in EDB Manager is automated--or if it is, I'm still testing it before putting into a job or the application. >> Okay. I got the impression that you were executing these scripts in the EDB Manager on an on-going basis as a part of a daily schedule. Thanks for clearing that up. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |