Will I use FE/BE?

[whiterower]

hi, I just wanna ask if i need to split my application into a be/fe. Right I'm thinking that I don't need to spli the database since most of my table resides on our SQL Server. What I did ii convert my db to mde wihtout splitting.Is this the right thing?

 

[Rob.Mills]

Are most or all of your tables on the SQL server? If all then you're better off using an Access Data Project. They're designed specifically for connecting to SQL Server.

 

[whiterower]

I can't since I have queries that use parameters and I already deployed my app..Yes all my tables resides n my SQL server.

What I did was i convert the mdb file to mde and install a copy on each machine..is there any effect that will slow down the apps?

 

[Pat Hartman]

I disagree with converting to a project. There are too many things that you can do in an .mdb that you can't do in an .adp and the .mdb supports SQL server just fine. In fact, the .mdb will support ANY back end that can be reached via ODBC. You can't say that about an .adp.

When your be is an ODBC datasource, you MUST use queries that take parameters to limit the number of rows returned as the recordsources for your forms and reports. Otherwise, you'll loose all the benefit of a "real" RDBMS. There is lots written on this subject here. You can also read the optimization FAQ's in the kb.

 

[whiterower]

Thanks Pat...I did just that i use parameters on my queries..my question is..is it okay if i convert the mdb into mde and don't have to split the db since all my tables is in my sql server? and i dont have tables in my access db its just queries,modules,reports and forms.

I convert the mdb to mde and distribute it to each users workstation..is this alright?

 

[Pat Hartman]

There is nothing to split. Your tables are already in another database (an SQL db). The "splitting" process removes Jet tables from one db and moves them to a second db and replaces the physical tables in the fe db with links to the tables which are now physically in the be db. In your case, there are no Jet tables in the fe since all your tables are contained in an SQL Server db.

Creating an .mde is not a problem. Just make sure that your .mdb is kept in a safe place since there is no way to "unconvert" an .mde. You will loose all ability to change your db objects if you loose the .mdb.

 

[whiterower]

Thanks Pat for making it clear...i appreciate it

 

[Rich]

What's the advantage of making an MDE?

 

[Pat Hartman]

It reduces the size of the db and usually speeds it up.
It minimizes the user's ability to cause accidental damage because the design views of forms/reports/modules are not available.

 

[Rich]

I read that making an MDE makes little or no difference to the speed

 

[Pat Hartman]

I think the speed enhancement is network dependent. I find that the db opens a little faster but others have reported significant improvements.