Temporary table solution for web db

I have created a hybrid Access application, but have the need for a temporary (local) table to exist in each users copy. This table will be used to allow each user to play some "what if" scenarios. By "hybrid Access application", I am talking about an Access application that has been published to SharePoint, but each user runs an Access file locally with the data being stored on SharePoint. This works very nicely allowing users to use native forms instead of dealing with the browser limitations.

Thanks, Dale
Dale LoganConsultantAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Connect With a Mentor Infotrakker SoftwareCommented:
Just add the table to the Access app, and don't publish that to Sharepoint. Or, create the table when the app is opened, and delete it when it's closed.

Here's a good collection of Access DDL functions:
http://allenbrowne.com/func-DDL.html
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
 Other option is to create a temp DB, create the table in there (number of ways to do that), then kill off the temp DB when your done.

Jim.
0
 
Dale LoganConsultantAuthor Commented:
LSM,

I checked out the solutions at the link you provided. My first thought was that there was no way I could pull that off. I am very weak when it comes to VBA. I attempted the one named: CreateTableDDL. When I ran it i get a user-defined ...error on the very first line:

Dim cmd As New ADODB.Command

Also, I don't think you can NOT publish something to SharePoint. When you sync, it gets everything.

Jim,

<create a temp DB, create the table in there >
Again, that may be over my head. Most of my users for this project are using Acces Runtime and don't have the full version of Access. Would your suggestion be possible then?

Thanks, Dale


 
0
 
Jim Dettman (Microsoft MVP/ EE MVE)Connect With a Mentor PresidentCommented:
Dale,

<<<create a temp DB, create the table in there >
Again, that may be over my head. Most of my users for this project are using Acces Runtime and don't have the full version of Access. Would your suggestion be possible then?>>

  Yes.  Here's an example of some VBA that creates a temp DB:

430       pb.SetMessage "Creating scratch database..."

          ' Set the temp database location\name
440       gstrTempDatabaseName = "C:\TravUtilsGLImport.MDB"

          ' Kill the temp database if it exists
450       On Error Resume Next
460       Kill gstrTempDatabaseName
470       On Error GoTo btnVerify_Error

          ' Create temp database
480       Set dbsNew = DBEngine.Workspaces(0).CreateDatabase(gstrTempDatabaseName, dbLangGeneral)

          ' Create table for transactions
490       DoCmd.TransferDatabase acExport, "Microsoft Access", gstrTempDatabaseName, acTable, "tblGLImportData_Template", "tblGLImportData", True

          ' Create errors table
500       DoCmd.TransferDatabase acExport, "Microsoft Access", gstrTempDatabaseName, acTable, "tblGLImportErrors_Template", "tblGLImportErrors", True


It's very stright forward.  Although what LSM suggested would work very well, especially if you added the compact on close option, which would reduce the size of the FE by reclaiming the deleted temp table space.

Jim.
0
All Courses

From novice to tech pro — start learning today.