Griff basically summed it up pretty well...
Now getting this into VB.NET seems to be your challenge... Usually this would become and Entity Framework Data First type of project, and the wizards could whip this up into an MVC rather simply; however you are going to find that many tutorials for this are going to be C# based and not VB- You may want to reconsider the language.
Now for the DB design...
You seem to have the basics down on table design if you are just going to be looking up verses; but that seems kinda easy. I am guessing you are going to want more than this; incorporating such features common Bibles have such as book/chapter synapses, concordance, and other "tags".
So you are most likely want to over-engineer the normalization to account for the "future expansions" which you will want to add after the basics are done.
Here I have added in two tables and augmented what you had; adding in a Sort Order and reference if it is Old or New Testament. Author and Synapses are common, other additions could be Start/End time as well as alternative names (Chronicles vs Paralipomenon) and which faiths accept it (Apocrypha).
CREATE TABLE Testament (
TestamentID SMALLINT Primary Key NOT NULL,
Testament NVARCHAR(3) NOT NULL
SortOrder INT NOT NULL,
Synapses NVARCHAR(MAX) NULL
)
GO
CREATE TABLE Book (
BookID INT IDENTITY(1,1) PRIMARY KEY NOT NULL,
TestamentID INT NOT NULL,
BookName NVARCHAR(64) NOT NULL,
SortOrder INT NOT NULL,
Author NVARCHAR(64) NULL,
Synapses NVARCHAR(MAX) NULL
)
GO
CREATE TABLE TestamentToBook (
ttbID INT IDENTITY(1,1) PRIMARY KEY NOT NULL,
TestamentID INT NOT NULL,
BookID INT NOT NULL
)
GO
Submit an article or tip