Split database

[LizJohnson]

I don't think it is on a local server. I know it is a shared drive. I believe it is a remote access drive.

I ended up creating copies of the existing database, including the back end. I re-linked the tables to the correct year database and then deleted all of the information that wasn't for that year.

Since the state isn't going to do anything about the drives, I figured this would be our best solution as the speed would only slow down ever more in the future as we continue to add to the database.

I want to thank ALL of you who have helped me with this. Because of your help, I was able to do this with little time spent. Since I am not a programmer, this help and this forum are invaluable to me.

 

[jdraw]

Liz,

With respect, you seem to be reacting to symptoms. Can you not talk to your IT department, or a techie involved in database/networks etc and have them give you an overview of the "technical side" of what you are dealing with?
-network
-server
-software

Who installs new/updates to software?
Who maintains your "network"?

You're working in a state government department, so this info should be available to you. You need it to do your job, as we can see from your posts.

You know --"Who you gonna call?"

Good luck.

 

[gemma-the-husky]

@Liz

out of interest, why do you need this on a (remote) server. Are your users spread about geographically?

 

[LizJohnson]

I wouldn't care if it was on a remote server or not. It's the systems department (IT) who determines this.

Everything we do as government employees goes onto the servers and is automatically backed up each night. We may have access to numerous drives, depending on our job duties.

It's a government thing.

 

[HiTechCoach]

I wouldn't care if it was on a remote server or not.

If you can about performance the you should care.

Remote Server = SLOOOOOOOOW and data corruption.

Everything we do as government employees goes onto the servers and is automatically backed up each night. We may have access to numerous drives, depending on our job duties.

It's a government thing.

Yep. Totally get it. I work with state agencies.

I have not worked with KY. I have a solution that other State's IT departs allow.

 

[LizJohnson]

Unfortunately, I've heard that the systems department doesn't really like Access too much. I think they think it takes up too much space.

I love it because I can create what I need without having to expend state resources to create something I need and I can usually fix problems (sometimes with this site's help). It also saves me time because by the time they write programming for a new system, I've come up with numerous changes. For the systems department, every new change requires more money!!!

I work with just a very small part of the government, so I'm sure they won't do anything, and even if they could, I don't think our supervisors would allow the money expenditure to do it.

Thanks again for your help.

 

[The_Doc_Man]

Liz, may I respectfully point out that you are approaching this like a martyr trying to save a department. (OK, that sounds a LITTLE extreme...).

If you get a management buy-in using cost savings as justification, then you can force the IT dunderheads (of which I sometimes WAS one...) to do a risk/reward study where the reward is less hours to do something (which translates to salary dollars) and the risk is not THAT severe for an in-house app with firewall protection around it.

To make progress, you MUST get a management buy-in because then you can get the boss to ride shotgun for you. Doing it yourself makes you a martyr. You know what happens to martyrs? Someone calls them out and hangs them out to dry. Get some political support and suddenly things get a LOT better.

You want to work for government? I spent over 28 years with various commands in the U.S. Navy as a contractor. Trust me, I KNOW what happens to projects that get - and that don't get - managerial buy-ins. With a management buy-in, you don't have to play politics. Someone else will do that for you. Or, they will hand you your head on a platter because the project wasn't that useful. But at least you will know.