A Couple General Questions.

[Breanna]

Hello,
I am brand new to Access and have started to create a database. Apon all the reading I have a few questions that I havent been able to find answers too in a way that I understand. With the questions I know there are websites with answers but as I said I am having trouble understanding the meaning behind it and would love someone to dumb it way down for me. Any information helps and is much appreciated.

1. Splitting the Database. I can see why this is important so I did a practice one to see if I could follow the steps. That part was fine but what I do not understand is that when I did this the Front end database had all the tables and all amounts of editing. I thought that those werent going to be there since the point of splitting was so that those things did not get messed up accidentally. I must be missing something here.

2. VBA code ending up in a continuous run: I created a form that required VBA code. When I finished it I showed my boss to see if he wanted any changes. Apon telling him it had code he freaked out saying that if I mess up the code it will put the database in a state of continuous circular running and that will freeze my laptop decoding everything that uses code and messing it all up (like even outlook, other programs that are not access) I tried looking online but didnt find anything helpful. Is this true? if so what can I do to prevent it? As someone who has never used VBA before that sounds scary because I know I am going to mess up the code.

Those are it for now. Thanks in advance!

 

[pbaldy]

1) You would still see the tables in the front end, but you should see a little arrow next to each indicating they are linked.

2) Every db I've ever built has VBA in it. Once in a great while it will get caught in a loop, but Ctl-Break should stop it. I certainly wouldn't avoid using VBA because of that concern.

 

[JHB]

...
2. ...When I finished it I showed my boss to see if he wanted any changes. Apon telling him it had code he freaked out saying that if I mess up the code it will put the database in a state of continuous circular running and that will freeze my laptop decoding everything that uses code and messing it all up (like even outlook, other programs that are not access) ...

Aha - never seen behaviour like this,(endless loop yeah - but messing up other programs code, never) so I would like to know where your boss has this information from, he maybe has had a bad day!

 

[gerrythefish]

2. VBA code ending up in a continuous run: I created a form that required VBA code. When I finished it I showed my boss to see if he wanted any changes. Apon telling him it had code he freaked out saying that if I mess up the code it will put the database in a state of continuous circular running and that will freeze my laptop decoding everything that uses code and messing it all up (like even outlook, other programs that are not access) I tried looking online but didnt find anything helpful. Is this true? if so what can I do to prevent it? As someone who has never used VBA before that sounds scary because I know I am going to mess up the code.

Its like saying "Dont drive that car - you might crash it and cause planes to fall out of the sky!"

If you havent caused an infinite loop then you arent trying hard enough. Ctrl - Break keys (the break key might be labelled Pause) works great to interrupt the code.

Of the few things Microsoft improved in the last decade or 2 - when a program crashes it is much much less likely to take another program down, with worst case being a computer restart, no real damage.

Although you could write code to impact other programs negatively - you would have to try hard to do that. Typically the worst you can do is an infininte loop or crash access requiring a restart of access.

Best way to stay out of trouble - find code to reuse (this forum, googling etc) and read thru and try to understand every line before you implement it.

Good Luck!

 

[Breanna]

All these post have been helpful thanks.