The strange thing is that I've created my V12 file a couple of months ago.
Yesterday they delivered me a new version of the database so I had to
recreate my V12 file. I worked allday long with that V12 file. Today also
and then I get the warning 1970. I now recreated it and the warnig has gone.
But now I'm worried that the end-user will get the error and the project has
to be finished today. So how can I be certain?
Thx
Tom
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Warren Stolow
Sent: Friday, March 02, 2001 7:21 PM
To: '[EMAIL PROTECTED]'
Subject: RE: <lingo-l> URGENT!!!!! V12 error
Hello Tom,
Why do you not contact me at my support address? INM supports
non-registered users and the response time would be quicker
then if you post to a list? Especially if it is an urgent matter!
Anyways, here is my answer:
Which version of V12-DBE are you presently using?
The following are a few reasons why you still might be seeing
the V12-DBE Splash Screen:
- You began your V12 experiments with a non-registered version
of V12. You then bought a license [Yea!], but failed to
open the database once in ReadWrite mode using the newly
registered version of the Xtra.
- You author with 2.x Xtra but are using 3.0 in your app
The registration numbers are not compatible!
- Using Create at runtime - your licensing agreement does not
allow for this functionality. Use mCloneDatabase instead!
Online Manual:
http://www.v12dbe.com/downloads/v12director/manual/v12-user-manual.pdf
Specifically: page 68 [Cloning]
- In a few rare cases your database was so corrupt that it can
not even be registered! Like one month of exiting your
application without closing any of your 15 tables in your
V12 database.....
- In even more extremely rare case's - the V12-DBE registration
number given to you is invalid! This is a tricky one to solve
and has happened only once, in four years, but it is a possibility.
Note that yours truly has an absolute 100% success rate in
regards to this issue, so we will find the solution even if
it is none of the above.
Enjoy your weekend Lingoists!
-Warren.
-----Original Message-----
From: Tom Vandenbossche [mailto:[EMAIL PROTECTED]]
Sent: March 2, 2001 10:44 AM
To: lingo
Subject: <lingo-l> URGENT!!!!! V12 error
Hi list
This is really urgent
I'm working with a V12 database in D8
I now get the error "1970: This database is still in demo mode. To legalize
it, please open it once in Readwrite mode."
I opened the database in readwrite mode with the line
set gDB = new(Xtra "V12dbe", the pathname & "data:data.V12", "Readwrite",
"top secret")
When I check the global gDB I see he has made a new child of the xtra V12
Why do I get the error and how can I solve this?
This problem has to be solved urgently
Thx for any help
Tom
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
