Click here to Skip to main content
14,422,439 members
Rate this:
Please Sign up or sign in to vote.
See more:
Hi,

I am new to the Vb.net and i am using Vb.net with Ms Access database.. I want to create bible software like

One Sheet

BookName | BookID
-----------------------------------
John | 50
-----------------------------------
Mathew | 51

etc....
another Sheet

BookID | Chapter | Verse | Text
------------------------------------------------------
50 | 1 | 25 | Text goes here
------------------------------------------------------
50 | 1 | 26 | Text goes here
------------------------------------------------------
etc...

What I have tried:

How to do this in my software? and how to search and filter and project Richtextbox1... Please help me on this...

I have loss my thinking because over 2.5 months i am trying this... 
Posted
Updated 7-Jan-20 2:54am
Comments
Maciej Los 7-Jan-20 2:43am
   
MS Access does NOT know sheets. It can holds tables!
Member 14621280 7-Jan-20 3:40am
   
Ya its table only

Table 1
BookName | BookID
-----------------------------------
John | 50
-----------------------------------
Mathew | 51
Table 2
BookID | Chapter | Verse | Text
------------------------------------------------------
50 | 1 | 25 | Text goes here
------------------------------------------------------
50 | 1 | 26 | Text goes here
------------------------------------------------------
etc...
F-ES Sitecore 7-Jan-20 4:39am
   
If you're looking to hold the entire Bible and (one would assume) have some kind of searching, then Access is not a good choice. I'd look toward one of the distributal SQL server based solutions.
Rate this:
Please Sign up or sign in to vote.

Solution 1

We can't help you at all based on that little - it's not at all obvious what you are trying to do, much less what you have tried, or where you are stuck.

Describing a project as "I want to create bible software" and then just slapping two "sheets" down in front of us with no idea what the connection between them is, or what your "Richtextbox" is supposed to do (or even where it is in relation to the two "sheets") doesn't help anyone. Particularly since we have no idea what a "sheet" actually is: is it a From? Or a DB Table since you mention Access? We don't know.

What I'd suggest is that you start at the beginning. Start by deciding what you are trying to produce. That can be as simple as "I wanna make a text editor" to a pretty solid idea of exactly what you want to use / sell.

Then decide what environment you want it to work in. It this Cloud based? Web? Windows? iPhone? Android? Linux? The more environments you add, the more complex you are making the job.

Then sit down and write a specification: describe how the app is going to do what it does. This should be reasonably full: It's not a development specification - it's a functional spec. It's "what the user sees" and "how the user interacts"

And that provides you with the next two design docs you need: the dev spec, and the test spec. The later is important - it gives you a "end point" for the project, a point at which you can start to consider releasing it.

You can then start using the dev spec to design the actual software ... but unless you do something like that to "formalise" the project, you don't have any strong idea of where you are heading, and on a largish project that's a bad idea because many of your initial decisions will be very, very wrong!
   
Rate this:
Please Sign up or sign in to vote.

Solution 2

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
   

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)




CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100