Hi Jim,

If I may be of any further help in providing background in the process I
went through it is my pleasure. I have received such a wealth of wise tips
via this fantastic list, and of course, from Razzak and John Minyo and the
"Dream Team" at RBTI over the years, that if I can help in any way it is
again, my pleasure!

Of course, the reason it took me 11 months is because of my own time
limitations; I did most of my work in what we call "overtime", which is just
a way of saying on my own time - typical for most small business IT projects
(in my experience). I elected to go through every line of code in all my 7.6
applications, in a 9.1(64) environment, redesigning a majority of forms and
reports, and writing a few new applications along the way. Along with
juggling my other corporate responsibilities it personally took me this
expanse of time.

When it came to actually running the conversion from 7.6 to 9.1: 3.38
minutes. A testimony of the efficacy of R:BASE and RBTI's stellar products!

Brad Davidson
Aero-Craft Hydraulics, Inc.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle
Sent: Saturday, August 25, 2012 5:31 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: Cannot Save a Revised Form (Error (122)) - Version
9.1.5.20816 (64)

Brad,

 

You make me feel good in stating you have been converting from 7.6 to
9.1 over the past eleven months.

I am in the process myself of converting over to 9.5 from 7.6.

I have not been at it that long but it is definitely a process.

I will keep this post and show it to the boss if he gets impatient.

 

James Belisle

 

Making Information Systems People Friendly Since 1990

 

 

________________________________

From: [email protected] [mailto:[email protected]] On Behalf Of Brad
Davidson
Sent: Friday, August 24, 2012 1:01 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Cannot Save a Revised Form (Error (122)) - Version
9.1.5.20816 (64)

 

I wonder if anyone else has seen this error and has some advice on what to
look for to resolve.

 

"Error - Column Sys_Form_Mod_TS must be a valid DateTime (122)"

 

After attempting to revise an object in form designer, noted changes were
not being saved. So, performed an unload/run on the entire database. Over
the years, this routine has cleared up a myriad of errors with our database.

 

After the rebuilding of the DB, and upon saving the form with minor
revision, got the error above. Happens for any/all forms - cannot save any
forms which have been revised, even with a simple pixel move of an existing
object.

 

So, checked out contents of Sys_Columns for this column to find it
references Sys_Table_ID of 24, which is the Sys_Forms3 system table.

 

Then, scanned down the column, Sys_Form_Mod_TS to see if there was any data
which was not a datetime value - they all look good to me.

 

Kinda lost at this point. Don't know if one of the forms have a corrupted
datetime column, or, should I be looking at the sys_forms3 table for
something else ??

 

Any ideas what else to look for? Have made a ton of form changes in past
3 weeks since converting from 7.6 to 9.1(64), an eleven month project for me
(updated syntax, redesigned forms, reports, and new menu driven EFF's,
etc...

 

Thank you!

 

Brad Davidson

Aero-Craft Hydraulics, Inc.

--- RBASE-L
================================================
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to [email protected]

(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: INTRO
================================================
TO UNSUBSCRIBE: 
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: UNSUBSCRIBE
================================================
TO SEARCH ARCHIVES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body, 
place any 
text to search for.
================================================


Reply via email to