Solved bible database

I reviewed the thread and see that you are getting some specific help, so I'll take a different direction and give you a bit of generic help. You need to look up the topic "Cascading Combo Boxes" to see how to make combo box B sensitive to the selection of Combo box A.

The technical comments you are getting regarding things like "Option Explicit" must not be ignored because until you resolve issues caused by "phantom variable creation" you won't be ABLE to get to the point of using a cascaded combo sequence.
 
You need
OPTION EXPLICIT
at the top of every module then try to compile your code

Come on now. You ever seen code like this? Not going to work.
Code:
Private Sub SelectedBook_Click()
Private Sub btnOpenVerses_Click()

    ' Ensure the combo box is not empty
    If Not IsNull(Me.cmbBookName) Then
        ' Use Nz() to avoid errors with null values and pass the second column (book name)
        Dim strBookName As String
        strBookName = Nz(Me.cmbBookName.Column(1), "")

        ' Open the Verses form and pass the selected book name in OpenArgs
        If strBookName <> "" Then
            DoCmd.OpenForm "VersesForm", , , , , , strBookName
        Else
            MsgBox "No book name found."
        End If
    Else
        MsgBox "Please select a book."
    End If

End Sub
End Sub
I will read up on option explicit, thank you
 
I believe your database structure has not been fully developed. Please be aware that I cannot provide an MS Access specific solution. My advice is generic. Additionally, I have not attempted to deconstruct the code what you have already developed.
  1. Based on the image you provided you need (a minimum) of three tables. One for Chapter, one for Verse, and one for Scripture.
  2. The Chapter table would have a minim of two fields: Primary Key field and a number (integer) field identifying the chapter. I usually have an "extra" field (in all tables) to allow notes or other miscellaneous stuff.
  3. The Verse table would be similar to the Chapter table. It would have a minimum of three fields. One, its own Primary Key field, a foreign key field that points back to the Chapter table, and then its own field for the Verse number.
  4. The Scripture table would also have a minimum of three fields. Its own Primary Key, a foreign key that points to the Verse table Primary Key, and a text field containing the actual scripture.
----------------------------------------------------------------------------------
Based on your image, when you click on the Chapter combobox (listbox), an SQL statement should be issued to populate the Verse combobox (listbox) with all verses that meet the criteria.
Then, when you select the Verse field, an SQL statement would be issued to show the Scripture selected based on the Verse field.
 
Last edited:
I will read up on option explicit, thank you

However that only fixes things going forward. You need to add it manually to existing code.
 
Thank you
When I login it gives me
Run time error 3044
It says my path is not a valid path I should make sure it's spelled correctly and that I'm connected to the server which the file resides.
What am I missing
I linked to the tables on my computer. You will have to relink using the link table manager.
 
As far as I can see, none of your tables have a Primary Key and you have no relationships defined
Hi bob just wanted to show you a diagram of my relationship structure as I cannot understand how is it that you don't see any defined relationships nor primary keys, I really value your insight, Thank You
 

Attachments

  • relationship diagram.png
    relationship diagram.png
    229.1 KB · Views: 10
Hi bob just wanted to show you a diagram of my relationship structure as I cannot understand how is it that you don't see any defined relationships nor primary keys, I really value your insight, Thank You
If you look at the backend db you posted, you will see that none of the tables has a PK. Anyway, since you have marked the thread as solved it's a moot point.
 
If you look at the backend db you posted, you will see that none of the tables has a PK. Anyway, since you have marked the thread as solved it's a moot point.
But that is not the real backend, that is only an import into access from the MySql database. I assume the PKs and relations did not port over. These seem to exist on the real BE.
 

Users who are viewing this thread

Back
Top Bottom