Access Stability

[tcox]

(Preface: I'm still very hot about access crashing)



Is it because my installation environment? Win7 enterprise, 4gb ram, core 2 duo. This workstation works great for all other software, including demanding CAD and rendering.
Is it because my save directory is an active directory? (network drive, 1 gigabit Sans)

I had a TON of code and a few controls done on a form and SAVED when prompted to when leaving that form.
Start creating a new form, need to look at it to check something, ALL work is gone, go to check the code behind, ACCESS CRASHES!!
On reload, the new form with its controls and code is still there, but all the previous work on my /was finished/ form is GONE!

I'm getting really pissed and tired of access crashing, loosing work etc.
Is this common or do I just have bad Juju?!

-Tevis

[ranman256]

It happens. Not too often , but does. I backup my work every hour or so.
I backup the production db, every day.
Backup,Backup,Backup.

Now I have had a PC, no different from the others, but would crash WAY too often, and sometimes corrupt the db with it. After many re-installs/repairs, the only fix was to NOT use that PC.
For some reason, certain PC are missing something, or have an old something that does this and I was never able to fix it.

[tcox]

Then I may be SOL. All the PC's here are imaged the same...
I had an i5 but it got taken away when IT did a re-image and updates, now I have a Core2Duo.. I'm running the latest version (2016 ). I should mention with that the crashing behavior has not changed!

I've been learning Visual Studio, .NET & C#, we have a web development team, and my boss wants me to make a complete DB in Access, and give it to the web development team as a template. =/ I wish it was developed in .NET to start. While the learning curve has been steep, everything has worked without fuss in Visual Studio and SQL Server Express.

[ItsMe]

I don't know that newer versions of Access crash more often than older ones. I have noticed that using SSMS and Visual Studio Ultimate on the same machine as Access seems to wreak havoc on Access. Of course, I don't know that it is Visual Studio. On thing that I truly believe is that Adobe CC does not play well with Access on the same machine.

When I am working in Access, I try to keep in mind that the Form designer and the VBA editor are two separate programs. So I am using Ctrl+S often and I try to keep the number of forms I have open in Design View to a minimum. I start to panic when I see the Save All option, indicating I have multiple forms that received edits.

[tcox]

The only software installed on the machine is Office 2016, Microsoft AX and Symantec Endpoint Protection.

Visual Studio and now Fusion 360 (CAD program) are accessed via Virtual Machine. (The server has the horse power and RAM to work with my 3D models after the workstation maxed out its 4gb of ram, and as a security policy we do not have any kind of server running on a workstation)

[ssanfu]

I've found a sure way to corruption (crashing) is to edit VBA code while code is executing. Maybe is doesn't happen immediately, but it will happen (at least to me ).

Always ensure code is not executing, make your changes, compile, save, then execute the code (click buttons, change control data, etc).

I also "Compact and Repair", save and close the dB. Then I create a copy, adding an underscore and a letter to the name. Frequency depends on the number of changes and how lucky you feel. (Well, do you fell lucky? Do you?)

So I might start out with "Database2015_12_21.accdb".
The first save would be "Database2015_12_21_a.accdb".
The next save would be "Database2015_12_21_b.accdb".

Tomorrow I make a copy of the last DB save from yesterday, renaming it with today's date>> "Database2015_12_22.accdb".
Then start with the letters for the save for that day. ("Database2015_12_22_a.accdb", "Database2015_12_22_b.accdb")

3 rules of computing:
1) Backup
2) Backup
3) Backup...

[tcox]

Just thought I would post another oddity.
Got a compile error message when running my DB forms after making/using an array and some other fiddling.
So, I start commenting out code to see where the problem is.. Got it to compile.. ok, start un-commenting out code to find the culprit.
Ended up with the exact same code! I made zero edits!
I know what your thinking.. "yea right.." Seriously.. I yanked out my headphones, said a few expletives and my face turned a few shades of red.
VBA and Access is truly bizarre.

Right now I'm working on reading a single record, populating the forms text boxes with current info, then as the user adds or changes anything, it gets dumped back into the array and appends the record.

See how this goes.

Thank your being here and supporting me while vent!

Void rulesOfComputing(){
Serial.println("3 Rules of Computing")
For(int i=1; i<=3; i++){
Serial.print(i)
Serial.println(") Backup")
}
}

There, I feel better.. I coded in C++

[ssanfu]

now, that was funny!


--------------------------------

I know what your thinking.. "yea right.." Seriously.. I yanked out my headphones, said a few expletives and my face turned a few shades of red.
VBA and Access is truly bizarre.

I feel the pain...

The access FE/BE was on my local computer and I would get an error something to the effect of "Lost connection to the internet". Being that I was not using the internet, I was lost/panicked. I checked all of my backups. All were corrupt. The corruption had been getting worse and worse over several months.
I eventually discovered that the VBA project was corrupt. I could still open the dB and see the forms/queries/reports and code; it took me a week, but I eventually figured out how to recover the dB.