ODBC connection and running something every hour or so

[lala]

i have more than 1 question and not sure if i should open a thread for each question or if combining them is ok.

if i shouldnt've combined them - i'm sorry.

1. is there a way to create an ODBC connection by code? so that i don't have to go on every computer and create the ODBC connection (I'm talking about going to the window below in case i'm using wrong words to describe it)

2. how do i run some code inside in Access db every few hours without using Windows Task Manager to open a database that has an autoexec macro?



3. I'm thinking of letting some computers use 2010 Access Runtime. i've never used it myself or had users use Runtime without having Access installed. does anyone know if there are issues?


thank you very much!!

 

[pbaldy]

1) It can be done in code, but you can also create a File DSN on the server and link your tables using that. Then nothing has to be done on each PC.

2) You can use the timer event of a form.

3) I have a few computers using the 2010 runtime (running 2000 mde's and 2007 accde's) with no problems thus far. With any runtime version you want to have good error handling, as an unhandled error will kick the user out of the program.

 

[lala]

thank you so much!!!!!!!!!!!!!!!

 

[pbaldy]

Happy to help!

 

[lala]

1) It can be done in code, but you can also create a File DSN on the server and link your tables using that. Then nothing has to be done on each PC.

can you explain the file dsn please? you mean creating a connection in the window above on the server and link my tables using that dsn file?????
that easy?

 

[pbaldy]

Yes, on the File DSN tab. I usually create a hidden shared directory on the server to hold them, though I don't know if that's required.

 

[lala]

Yes, on the File DSN tab. I usually create a hidden shared directory on the server to hold them, though I don't know if that's required.

wow, thank you again. i can't believe the pain i've been going thru))))

 

[lala]

ETA never mind, i said something stupid as usual.

 

[lala]

1) It can be done in code, but you can also create a File DSN on the server and link your tables using that. Then nothing has to be done on each PC.

hi, so i'm now up to this point. i set up a file DSN on the server and it works fine on one computer but when i try to open the database on another - it doesn't.

here's my File DSN

[ODBC]
DRIVER=SQL Server
UID=natalie
DATABASE=MY DATABASE NAME
WSID=COMPUTER NAME DSN WAS SETUP ON
APP=Microsoft® Windows® Operating System
Trusted_Connection=Yes
SERVER=MYSERVER\MYSQLSERVER


the connection looks to be computer and user-specific. is that the problem?

the way i understood the purpose of a file DSN is to avoid having to create ODBC connections on each computer. so i thought that i create one front end that links to the FileDSN and it will then work on any computer. am i wrong?
thank you

 

[pbaldy]

That is how it should work, yes. I never do anything on the user PC's. I'm not at work so can't see a DSN's properties, but offhand the only thing that stands out is that I use a SQL Server login rather than Trusted Connection. A quick Google reveals this:

http://www.ehow.com/how_5232278_create-trusted-sql-server-connection.html

Does that help?

 

[lala]

i think they're just explaining how to create an account for the sql server. or am i missing something on that page?

i already have an account that has access to the SQL server.
and i didn't understand, what do you put instead of the TRUSTED CONNECTION line?

 

[lala]

never mind, i'm an idiot, everything works, thank you

 

[pbaldy]

Ah good, glad you got it sorted out. I was finally at a point where I could remote into a work server.