Hello all,
I recently split my database and there are two issues I was hoping the experts could help me clear up.
1. I have a shortcut pointing to the database file that opens the form and minimizes Access, so the user only sees the form. The way I do this is in the link below (very simple)
https://accessexperts.com/blog/2015/...cess-tutorial/
However, ever since I split my database, something funky happens. The form opens as usual which is just some buttons that open up other forms. When I click on one of those buttons, I get a run-time error 2046 that says, "The command or action 'GoToRecord' isn't available". When I debug, it points to a line of code that I have:
Code:
Private Sub Form_Load()
DoCmd.GoToRecord , , acNewRec
End Sub
If I remember correctly, I only added this line of code because when the form opened it would also show the first record in the table but I wanted it to be blank. The funny party is, once I close the error I can then close and open the form without getting the error.
So, is there another way to make this form open without Access opening on the screen, as well? I know I can't keep the shortcut I made anyways because it defeats the purpose of splitting the database since I have to put the front end on a server anyways and create a shortcut to it, so it's like I'm making a shortcut of a shortcut.
2. This one isn't very important and is more of a noob question but if anyone has the time to read. I thought splitting the database would make the front-end file much smaller while keeping the data in the backend. However, it did it backwards. The front-end file is 8 mb and the back-end file is less than a mb. It's a small database now but I'm confused, I thought the purpose was so you could use the front end to distribute to the users, meaning the smaller the file...the better. As I add forms I can see the front end file getting larger and larger to the point where distributing it is more of a pain than the benefit of splitting it in the first place. Am I just seeing this wrong because my database is so small? Once the front end file gets over 25mb, I can't email it to the users (email attachment cap) and they will have to download it from a server, but everything I've read says users won't have to interface with servers after splitting because all of the data is only in the back end. I'm just not seeing any purpose to splitting if the data has to traverse the network anyways, so bandwidth is still going to be a problem, right?