splitting a db

[lipin]

Instead of using the database splitter wizard, can you just make a copy of db, then in the back end, just delete all the queries, forms, reports, and link the tables to the front end? Or is the splitter easier?

 

[Autoeng]

You can do either but the splitter makes it easier. If you do it manually you will have to establish you links to the backend manually as well.

Autoeng

 

[eforce]

Linking to SQL Server?

Hello,
I'm using 1 table & 1 Form for simplicity in explaining myself.

Problem: I have a MSAccess DB with Table1 & Form1 with Table1 as it's record source.

I have lets say 100 users with MSAcess (or Runtime) around the U.S. that would have the front end which consist of Form1

What are the steps I would take in order to make it so the 100 users can access the backend server which resides with me.

I'll be going with the MDSE SQL server but how do I configure this.

I messed around with the DB Splitter as well as the upsizing wizard. I can sort of make some sense out of it but I need a step by step manual or website that can show me this and explain how it works.

Eforce

 

[sratey]

Are you talking about Splitting the Database (seperating the forms from the Tables) and then replicating the Table db?

 

[eforce]

Hey & thanks for responding so quickly,

I know what splitting the db is and I know what upsizing does. What do I do with my split db (backend) and upsized db? How do I use my front end to access the back end? I want to know this step by step. I would also like to use the MSDE as the server and maybe after I learn all of this I can use the latest SQL server software.

Thanks,

 

[sratey]

OK, got the scope of your quesiton.

I will try to help.

1. Open the frontend db(if you have modified the menues for that db, you need to open it with 'programming' accessibility)

2. Access the 'Tools' pull-down menu

3. Select the 'Database Utilities' sub-menu

4. Invoke the 'Linked Tables Manager' command.

A. This is where the benefit of splitting the db using the
Wizard comes into play. When you use the Wizard,
MSAccess initiates a 'protocall' where every record in every
Linked table is given a unique identification number. It is
through this 'protocall' that MSAccess is able to replicate the
Tables protion of your application and still avoid corrupting
data.
Each and every record will be unique because of the
identifier. Another benefit to some applications is the ability
to 'Synchronize' the tables db.
5. This will bring up a GUI where you 'Select the linked tables to be updated:'. In this GUI you accomplish 2 different objectives.
A. You tell you db where the file is to link to. You do this by
selecting the option box at the bottom; 'Always prompt for
new location'
B. You select the actual table you want to link to your front-
end db.
6. Once you have made the appropriate selections, you make use of the command buttons on the right of the GUI.

That's all there is to the process. There are others out there who are much more knowledgable about it than I am. So I hope if they see some misnomers or other areas where this could be refined they will jump in there and make the clarification.

Hope this helps some.
If I can be of further assistance, don't hesitate to ask.