K
Kevin
hey,
I just upsized my first access db to adp and an sql db. The sql server is
not in the same bldg as me -- I am in WA and it is in OH.
The upsizing wizard seems to have done its job. I can login into the sql
server and see the db in Enterprise Manager. But when I open the access
front end on my desktop -- the front end app is pretty much froze up.
I have beern trying to open a form (that uses subforms) and it is almost
like the app is downloading all the data from the sql server -- and until it
does, it seemingly won't let me browse records -- I can't move from record
to record -- the calculating message appears in the status bar (what is it
calculating?) --
So I must be doing something wrong -- can anyone tell me what is wrong or
point me to some docs that discuss upsizing an mdb -- the use of forms and
subforms, etc.
Is it best to just use Access and link to the tables on the sql server?
thanks
I just upsized my first access db to adp and an sql db. The sql server is
not in the same bldg as me -- I am in WA and it is in OH.
The upsizing wizard seems to have done its job. I can login into the sql
server and see the db in Enterprise Manager. But when I open the access
front end on my desktop -- the front end app is pretty much froze up.
I have beern trying to open a form (that uses subforms) and it is almost
like the app is downloading all the data from the sql server -- and until it
does, it seemingly won't let me browse records -- I can't move from record
to record -- the calculating message appears in the status bar (what is it
calculating?) --
So I must be doing something wrong -- can anyone tell me what is wrong or
point me to some docs that discuss upsizing an mdb -- the use of forms and
subforms, etc.
Is it best to just use Access and link to the tables on the sql server?
thanks