Backup (or Export) all Code at Once

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is there a way to backup all of my code in one fell swoop?
Also, is there a way to get a text version of all of my controls programming
etc?
Assuming that from what I've heard about Access you can write all of the FE
in VB?

Thanks,

-David
 
You can write the FE in VB, but Access is better suited, because its
controls are specifically designed to be used with database objects, whereas
VB's aren't. (The same isn't true of VB.Net, though: VB.Net's bound controls
are good)

To backup all your code, make a copy of the MDB file.

To get a text version, take a look at what Arvin Meyer has at
http://www.datastrat.com/Code/DocDatabase.txt
 
Douglas J Steele said:
You can write the FE in VB, but Access is better suited, because its
controls are specifically designed to be used with database objects, whereas
VB's aren't. (The same isn't true of VB.Net, though: VB.Net's bound controls
are good)

Good to know.
To backup all your code, make a copy of the MDB file.

Yep, once or twice a day, sometimes more.
To get a text version, take a look at what Arvin Meyer has at
http://www.datastrat.com/Code/DocDatabase.txt

Thanks, this looks very helpful!

-David
 
You can write the FE in VB, but Access is better suited, because its
controls are specifically designed to be used with database objects,
whereas
VB's aren't. (The same isn't true of VB.Net, though: VB.Net's bound
controls
are good)

It's usually recommended to use Access instead of VB to build the FE because
the development is much quicker.
But if one uses VB.NET, is it possible to develops apps with the same or
near the same speed as doing it in Access?

Jesper
 
Jesper Fjølner said:
It's usually recommended to use Access instead of VB to build the FE because
the development is much quicker.
But if one uses VB.NET, is it possible to develops apps with the same or
near the same speed as doing it in Access?

Not if I'm building them, as I have very little experience with VB.Net, so I
have to look everything up! <g>

Seriously, though, I've heard from people with experience in both that
Access is still quicker for development.
 
It's usually recommended to use Access instead of VB to build the FE
because

Not if I'm building them, as I have very little experience with VB.Net, so
I
have to look everything up! <g>

Seriously, though, I've heard from people with experience in both that
Access is still quicker for development.

Ok thanks. I'm sticking with Access. To much of a learning curve I think
with VB.NET since this i pure hobby for me :-)


Jesper
 
Ok thanks. I'm sticking with Access. To much of a learning curve I think
with VB.NET since this i pure hobby for me :-)

It's horses for courses. In vb.net you get proper date picker control,
proper grids, far more control over the windows and a much richer event
model. Access does not even provide a proper combo list box(i.e. without a
drop-down).

For much work, Access is much quicker; but if you need to step out of the
box then it gets much harder than other programming languages. Having been
reading these groups for a while, I know better than to say anything is
impossible in Access, but even giving the user a simple calendar to pick a
date from takes pages and page of code, API calls, etc etc.

All the best


Tim F
 
"It's horses for courses"? I've not heard that expression... What's it mean?

Fred Boer
 
Fred, Fred, Fred. Google is your friend! <g>

Yeah, but he never invites me out for a beer...

Ok, I *should* have looked it up, but sometimes I just like human
interaction as opposed to living with the machine... ;)

Cheers!
Fred
 
Back
Top