Stand-alone Form?

[dgmorr]

Hi Guys,

I'm somewhat of an Access newbie. I was wondering if I could convert the form I created to some sort of stand alone program, or be able to have the form functionality in an Excel sheet? If not, then what are forms used for if you must transport the entire database with it?

 

[Niniel]

Oh man, those are a lot of different questions.
Let me try to answer some of them.

Forms are used to enter data into your database, and also to display some information. One way of looking at a form is actually called the Datasheet View, which does resemble a spreadsheet.
You sound like you are approaching Access with Excel in mind. However, it is quite a different beast, and I can only urge you to forget about Excel when you are dealing with Access, even though raw tables may look like spreadsheets. They are not.
In fact, are you sure you need a relational database, or might you be better off [continuing to work] with Excel?

As for form portability, when you start a new Access project, forms and data tables are together in one file. However, once an application is working, it is often split into a part called "back end" that holds the tables, and a part called "front end" that holds the forms, queries, reports etc. The back end is typically placed on a network drive, and all the people who need to work with the database get a copy of the front end on their computers. That way, you have only one set of tables, but several copies of the forms.

 

[dgmorr]

Oh man, those are a lot of different questions.
Let me try to answer some of them.

Forms are used to enter data into your database, and also to display some information. One way of looking at a form is actually called the Datasheet View, which does resemble a spreadsheet.
You sound like you are approaching Access with Excel in mind. However, it is quite a different beast, and I can only urge you to forget about Excel when you are dealing with Access, even though raw tables may look like spreadsheets. They are not.
In fact, are you sure you need a relational database, or might you be better off [continuing to work] with Excel?

As for form portability, when you start a new Access project, forms and data tables are together in one file. However, once an application is working, it is often split into a part called "back end" that holds the tables, and a part called "front end" that holds the forms, queries, reports etc. The back end is typically placed on a network drive, and all the people who need to work with the database get a copy of the front end on their computers. That way, you have only one set of tables, but several copies of the forms.

I am working with a rather large database, so I need to use Access (Excel was starting to crash on me). Is there a way to convert the Form to a front end type of program? Or will this have to be made through VB or some other language? I basically need the end user to be able to view data in some locked text boxes, and make updates to a couple different fields.

 

[dgmorr]

I am looking to create a program to access my database. I am more of a database guy, and not a programmer. This is my first time REALLY using Access though.

I would like to create a program which looks like this form I have created, but to work as a stand alone application.


I've blanked out some of the specific names, this is why the form is formatted a little funny.

I hope this can help though.

 

[Niniel]

Hm, if you want to create a standalone "program", then you may need to look for help in a programming newsgroup.
With Access, you can create forms that access other SQL dbs, but for this to work, all users have to have Access installed on their computer. Or you need to purchase a special version of Access with a runtime that you can then distribute together with your access application. Maybe that is what you are looking for?

 

[dgmorr]

Hm, if you want to create a standalone "program", then you may need to look for help in a programming newsgroup.
With Access, you can create forms that access other SQL dbs, but for this to work, all users have to have Access installed on their computer. Or you need to purchase a special version of Access with a runtime that you can then distribute together with your access application. Maybe that is what you are looking for?

That is pretty much what I had in mind. What version of Access would that be?

 

[Mile-O]

If you want a standalone, you are going to have to use something like Visual Basic 6, Visual Basic.NET, etc. to create a program and a subsequent executable, install it on each user's machine. You will still need the database on the server in order to connect to it via your standalone executable.