Splitting a Database

[carols]

I have created a database with a switchboard and command
controls within some of the forms. When I split the
database using the Database Splitter utility, I can see
the forms, but none of the commands will work. An error
message comes up with "expression error" type message.
Does anyone know how to split the database and have all
the commands that are programmed in usable? Thanks!

 

[John Vinson]

I have created a database with a switchboard and command
controls within some of the forms. When I split the
database using the Database Splitter utility, I can see
the forms, but none of the commands will work. An error
message comes up with "expression error" type message.
Does anyone know how to split the database and have all
the commands that are programmed in usable? Thanks!

Annoyingly, the people who programmed the database splitter wizard
didn't talk to the people who programmed the switchboard wizard; as a
result, the splitter makes the switchboard unusable.

Solution: Open the frontend database, holding down the SHIFT key if
you need to bypass the startup form. Delete the table (linked table,
should have an arrow by it) named Switchboard. Then use File... Get
External Data... Import to import the table Switchboard from the
backend (rather than linking it as the splitter wizard does).

Test the database; if it works, open the backend database and delete
the (now redundant) Switchboard table.

John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps

 

[Mike Labosh]

Annoyingly, the people who programmed the database splitter wizard

didn't talk to the people who programmed the switchboard wizard; as a
result, the splitter makes the switchboard unusable.

Heh. What a surprise.

Solution: Open the frontend database, holding down the SHIFT key if
you need to bypass the startup form. Delete the table (linked table,
should have an arrow by it) named Switchboard. Then use File... Get
External Data... Import to import the table Switchboard from the
backend (rather than linking it as the splitter wizard does).

This is interesting, but why would the switchboard form care if the table is
linked or native?

--
Peace & happy computing,

Mike Labosh, MCSD

Feed the children!
Save the whales!
Free the mallocs!

 

[Guest]

Thank you for the information, but it did not work. Not only do the
Switchboard commands not work, but also any other command within a form does
not work. I tried downloading Service Pack 1a and then Service Pack 3, but
it will not load. Do you have any other suggestions?

 

[Guest]

Thank you for the information, but it did not work. Not only do the commands
from the switchboard not work, but also any other commands that have been
added as an event procedure do not work. Do you have any other suggestions?

 

[John Vinson]

Thank you for the information, but it did not work. Not only do the
Switchboard commands not work, but also any other command within a form does
not work. I tried downloading Service Pack 1a and then Service Pack 3, but
it will not load. Do you have any other suggestions?

It probably has nothing whatsoever to do with the service packs.

Please post the exact error message that you get, and a description of
the actions that you take which generate the message. Did you keep a
backup copy of the unsplit (working, I presume) database?

John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps

 

[Guest]

I used the instructions on splitting a database. I first created a blank
database - back end - and imported the tables from the original. I then
created another blank database - front end - and linked the tables from the
back end database. I then imported all the queries, forms, reports. When I
open the front end database, the switchboard does not open, so I just opened
the switchboard form and I get the following message:

"The expression On Open you entered as the event property setting produced
teh following error: Error accessing file. Netowrk connection may have been
lost.
* The expression may not result in hte name of a macro, the name of a
user-defined function, or [Event Procedure]
*There may have been an error evaluating hte function, event, or macro."

Then I thought that maybe it was just the switchboard and I needed to go
into the Switchboard manager and "relink" the forms. This also did not work.
I then went into an individual form, which opened, but any command buttons
that have been programmed in do not work. I get the same message as above.
Any ideas?

Thank you for your help!

 

[Guest]

Why not just create your own switchboard? i.e., a form with links to other
forms, which can have their own links, etc.

You would have more control as to how it works and looks. I never liked the
way the switchboard looked or worked; or how it had to be configured. I
finally gave up and created my own.

Just a thought.
Hope that helps.
JMorrell

I used the instructions on splitting a database. I first created a blank
database - back end - and imported the tables from the original. I then
created another blank database - front end - and linked the tables from the
back end database. I then imported all the queries, forms, reports. When I
open the front end database, the switchboard does not open, so I just opened
the switchboard form and I get the following message:

"The expression On Open you entered as the event property setting produced
teh following error: Error accessing file. Netowrk connection may have been
lost.
* The expression may not result in hte name of a macro, the name of a
user-defined function, or [Event Procedure]
*There may have been an error evaluating hte function, event, or macro."

Then I thought that maybe it was just the switchboard and I needed to go
into the Switchboard manager and "relink" the forms. This also did not work.
I then went into an individual form, which opened, but any command buttons
that have been programmed in do not work. I get the same message as above.
Any ideas?

Thank you for your help!

It probably has nothing whatsoever to do with the service packs.

Please post the exact error message that you get, and a description of
the actions that you take which generate the message. Did you keep a
backup copy of the unsplit (working, I presume) database?

John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps

 

[John Vinson]

"The expression On Open you entered as the event property setting produced
teh following error: Error accessing file. Netowrk connection may have been
lost.

This may be a rather nasty bug. Are you running the original version
of Access2000 by chance?

See

http://support.microsoft.com/?id=304548


John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps

 

[Mike Labosh]

I used the instructions on splitting a database. I first created a blank

database - back end - and imported the tables from the original. I then
created another blank database - front end - and linked the tables from
the
back end database. I then imported all the queries, forms, reports. When
I
open the front end database, the switchboard does not open, so I just
opened
the switchboard form and I get the following message:

You say that you imported all the queries, forms and reports to your
front-end database.

You also have to import to it all the macros and modules.

Here's the simple way that I do it:

1. From my whole application that needs to be split, I close it
2. Create a new empty database and open it
3. Import all tables from the whole application to the empty database
4. Open my whole application database, delete the tables and link them from
the backend

Now, my whole application mdb file is now the front end.

In any case, It is not enough to just have queries, forms & reports in the
frontend. You have to have *everything* but the tables.
--
Peace & happy computing,

Mike Labosh, MCSD

Feed the children!
Save the whales!
Free the mallocs!