My first Micrsoft Access problem was linking. I remember back in about 1994 when I was an Informix DBA and programmer. Our company purchased some data-mining software to monitor our production data. As part of this project, the software company had to produce an Access 2 database to manage the production data. The first version of the database came out, and our company tested it and made comments.

The second version of the software was delivered, and we hired a data entry temp to punch thousands of lines of data into it. Naturally, the instant real data had to be added to the database and issues arose, we contacted the developer. He came back with these comments: "You will have to stop the data entry, put the database on a floppy disk, send it to me by courier, and I will send it back when I've made the changes (in two days)."

This process was not ideal from our company's point of view, so I started to read the help manual (yes, there was one in those days), and there on page 13 was a section that detailed the importance of splitting the database. We informed the developer (who, we found out, was new to Access), and he promptly split the database and our data entry temp got back to work. So too did the developer!

If there is a managers takeaway to this story, it is that  it helps if you can look your developer in the eye and give him well researched advice like I did with the Database Splitting wizard.
 


Comments

Michael Lewis
06/08/2012 6:04pm

My first Access job was also mid1990s in Access2. I was a Fortran/PrimeInformation(Pick)/AdvancedRevelation(Pick) programmer and I forget how, but I was invited to produce an Access database because their current one was not working.

I arrived at the place and found that their non-working database was in AdvancedRevelation - I fixed the problem in 20 minutes BUT they stll wanted to go modern and change it to Access.

I learnt on the job - even paid a colleague who was proficient in both Access and Arev to "teach" me. He was really jealous that I had the Access job and he the expert, didn't.

I got the job done and learnt a lot. As part of my reading I found the comments about splitting and so they ended up with both "progs" and "data". I still use the terms Progs... and Data... to this very day.

However I have had a client who wanted to forever move the one database with him from machine to machine. I actually rejoined the data and the "progs" as a single db was more convenient.

Still at it in 2012 - Access/vba/rest of Office as necessary. An "expert" who really knows only a tiny percent of what's available but who can push his envelope as required.

Reply
06/09/2012 1:03am

The split view thing you learn in Access is not just great, it is brilliant. During prototyping I always stay with one mdb-file, before delivering first production version I split. The split is easy to comprehend for most customers, this DATA.mdb is your responsibility and the SYST.mdb is mine. The only drawback is when you have to change DB-design, because then I have to do double maintenance. The last years I have also started to implement the same philosophy when working with SQL Server, I have my DATA-database where all the data-stuff is stored and then a bunch of system databases containing views, functions and stored procedures for specific applications using the DATA-database, the naming scheme (DBname.dbo.TableName) of SQL Server makes it rather easy and I have not seen any drawbacks in performance. /Rickard

Reply
FBarbs
06/11/2012 8:07am

Hi Everyone, Just wondering what the most common drawback is for splitting a database, and how did you overcome that problem? I can see issues coming up when accessing the database from a shared network drive.

Reply
06/12/2012 8:50pm

Hi FBarbs, there are no real drawbacks for splitting. One of them is that you can't use the Seek command directly - you must use FindFirst instead, though you can do some extra programming to use Seek against in another workspace. Splitting over a network is actually an advantage. Since the front end is stored locally, it loads faster, while only the data is shared from the network location.

If you split, you're welcome to use our free J Street Access Relinker utility at www.JStreetTech.com/downloads. Much nicer than the built-in Linked Table Manager.

Cheers,
Armen

Reply



Leave a Reply