Replies

Hi Hans,

I wasn’t being dense. Bad example.

Thanks again.

Thanks for responding Hans and Charlotte.

From your posts forms do not have a rst property but, “It can be the name of a table, or the name of a query, or a SQL string.”

Any ideas on a naming convention as to how from the OnOpen Event of the form in DB2, I can let the form know that I am using the query from DB1.

I tried Me.RecordSource = dbs.QueryDefs(“qry_EditRecords”) Type mismatch.

Thanks

Thanks for the info.

Thanks Wendell, Hans, and Charlotte.

Hans, your code is just what I was looking for.

Wendell, when you use a library database how are you calling the functions and what type of overhead is there over a Novell and/or MS network?

Charlotte,
___________________________________________________________________
You totally lost me here. Do you mean pass the functions to the created *module*?
___________________________________________________________________

Yes. My plan was to pass the entire function into the newly created module. Sorry for the confusion.

Hi Charlotte,

Do you have detailed instructions or code that attaches to SQL Server Views from Access 97?

Thanks

Hi Wendell,

Thanks for responding. I guess the answer is both.

The problem I am trying to solve:

I now have several functions that I use in most of my projects and my thought was to place them in a table. When beginning a new project I would like to select the functions I will use, auto-create one function, and pass the functions I will use in that project to the created function.

The academic exercise:

If a module can be created with DoCmd.RunCommand acCmdNewObjectModule, when and why would you use this, and how would you programmatically name and save the module?

Try importing the table from DB(A) into DB© bypassing DB(.

Thanks Sam. Your answer worked great.

Post your Macro to the list.

Right mouse click on your macro

Left mouse click on Save As/Export

Select “Save as Visual Basic Module”

Select Convert

Click on the Modules Tab

Copy and post the contents of the “Converted Macro- Your Macro Name”

This might help

Forms!NameOfYourForm![NameOfControlOnYourForm].SetFocus

Are you working with a form?

The fastest would be for you to convey the username and password that you have been using.

But, for possible future use of the database and maintenance, you might want to create a group with the same permissions that you have. Make each site user a member of the group, or, create one user for each site if their are multiple users at each site.

Sometimes projects that have ended have been resurrected.

HTH

Try:

Dim strTempFolder as String

strTempFolder = Dir( “C:TempConvert”)

If strTempFolder = “” Then

MkDir strTempFolder
SetAttr “C:TempConvert”, vbHidden ‘ Set folder with hidden attribute.
End If

Yes. [Currentuser] is a special word to denote who is using the database at the moment. No, you don’t need any code to determine the [Currentuser].

Search on CurrentUser Function in the help files to get a detailed explanation.

Set the controls property for the controls you are going to turn on and off to Visible = False

In the OnCurrent event of your form

If ([CurrentUser] = “Bob”) Or ([CurrentUser] = “Jeff”) Then
Forms!Combobox1.Visible = True
Forms!Combobox2.Visible = True
End If

[CurrentUser] holds the name of whoever logged in to the DB.

When Phil logs in the controls are all ready set to Visible = False