Microsoft Access 2016: Split Database to Frontend and Backend

Рет қаралды 50,560

Күн бұрын

Пікірлер: 15

@venkatyalamati3285 2 жыл бұрын

Thanks for the tutorial sir.. I am having one problem with my front end file. After splitting, if I change the location or name of back-end file, the front end file is not opening. Even with holding shift-key, the access application simply opening to it's default screen asking to create a new database but my front end objects not visible... Plz tell me the solution for this

@SteveMartinUSA 4 жыл бұрын

I want to be able to modify the forms, reports, queries, and even tables independent of the production version that people are using. What is the preferred way for an MS Access developer to prepare the next version of the application while users are accessing the current production version? How could you migrate the data to the new version?

@bessieammons4106 2 жыл бұрын

After database can you still add a table?

@garycurtis 3 жыл бұрын

Excellent video, thank you so much. Question, after splitting should the relationships be created on the front or backend? I see they migrated to the backend, but do I need them in the front end too?

@SteveMartinUSA 4 жыл бұрын

What's a Switchboard? This example uses under 2MB, but in a larger split it would make sense to compact to reduce the size of the front end files.

@alfredzkhanlakibul8494 Жыл бұрын

nice this is what im looking

@เกษตรกุ้มตนเอง 4 жыл бұрын

Hi Kirt, can you advice, when i copy the file and try to open in new computer but not work

@brandoncarraway1391 4 жыл бұрын

So I split the DB and placed the _be in a network drive - how do I give each user their own front-end? Do I give them a copy of the original DB prior to splitting?

@nimratalat1411 4 жыл бұрын

same question

@Bcarr122391 4 жыл бұрын

fungus dabogeyman thank you! I’ve actually gotten pretty advanced with Access since this question, and found the beauty of using SharePoint for the backend data; we experience an issue where our network server would quickly disconnect and reconnect from the network, causing a data disconnect, forcing us to close and reopen the database 🤦🏼‍♂️. Share point fixed this.