The New Language Reference (Local)

General
#1

The New Language Reference (Local): 2016R1.1 / OS X 10.11.5…

1. New Project, 2. Open the new Language Reference, 3. Cmd-Option-M 4. Type in the Method name: "SQLite_" (without the quotes) 5. Click in the Language Reference

enjoy the flickering, but this is not the end (but near) !

6. In the Language Reference, type SQLIte, click in SQLiteDatabase, 7. Choose the first code example, 8. Click in the Code Area, 9. Cmd-V, or Edit-Paste or even back to the Language Reference and drag and drop the code…

NOTHING !

Tip: close the Language Reference window and you will be able to paste the code.

In the example:

[code]Dim sql As Text
sql = “DELETE FROM Team WHERE ID = ?!”

’ Pass in values after sql instead of doing string replacement
Try
Dim ID As Integer = 100 ’ Primary key for row
DB.SQLExecute(sql, ID) ’ Previously connected database
Catch e As SQLiteException
Dim err As Text = e.Reason
End Try[/code]

DB from DB.SQLExecute does not exists: I inderstand. But when I declare one, I get an error in ID.

Also SQLiteException is unknow in Catch e As SQLiteException

Then, I shutdown the computer and go to bed.

#2

That kind of SQLExecute is in the new framework for iOS only. I have a small feeling you were trying to use it elsewhere.

#3

The New Language Reference (Local): 2016R1.1 / OS X 10.11.5…

  1. New Project,
  2. Open the new Language Reference,
  3. Cmd-Option-M
  4. Type in the Method name: “SQLite_” (without the quotes)
  5. Click in the Language Reference
  6. In the Language Reference, type SQLIte, click in SQLiteDatabase,
  7. Choose the first code example, press cmd-C
  8. Click in the Code Area,
  9. Cmd-V, or Edit-Paste

Now this is one of those areas where there is a bug in the local reference.
We have 2 SqliteDatabases and associated recordsets etc - one in the classic framework and one for the new framework.
But they have the exact same name and the only distinction is what kind of project you can use them in.
We’ll have to correct that issue.

The result is that when the local documentation set is created the dev center entries overwrite the older wiki ones and because this class is named exactly the same, has the same scope etc, we end up with only one of the two entries in the database.

#4