ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Crystal Reports, ODBC & Access >> Access General Issues >> Payroll master
http://www.istechforum.com/YaBB.pl?num=1224092476

Message started by cathyh on 10/15/08 at 10:41:16

Title: Payroll master
Post by cathyh on 10/15/08 at 10:41:16

I am looking for the Payroll department default GL account information.

When I try to open the BKPRMSTR table in Access, I get a table too large error, access completely locks, and I have to CTRL/ALT/DEL to get out.
Does anyone know what's causing this and how to it?

Is there a different table I should be looking at for this information?

Title: Re: Payroll master
Post by Kelloggs on 10/15/08 at 11:21:42

Try PR-M for the Default Payroll
The reason why you cannt open the table is because one of the records has a data on a field that does not correspont the field's data type.
It is suggested not to link a table, because of record locking issues.
Use a "Pass-through Query" = "SELECT * FROM BKPRMSTR"

:P

Kelloggs

Title: Re: Payroll master
Post by cathyh on 10/15/08 at 11:32:45

I have entered the department(division) defaults in PR-M. What I am looking for is a way to access the information I have entered for a report.

I have always set up my Access databases to pull from Evo by linking tables as read only. Then I write queries to access the data and reports using the queries. Users only see the list of reports. I rarely even look at the tables except to see the field names.

Is this a bad idea?

Title: Re: Payroll master
Post by Kelloggs on 10/15/08 at 11:56:05

I personally dont like to link tables, other people could have another opinion.
Try this:

1.- Create a Pass-through Query. I call it DBA
2.- Create a Module with the following function:

Function get_data()
Dim sqlString As String
sqlString = "SELECT * FROM BKPRMSTR"
CurrentDb.QueryDefs("DBA").SQL = sqlString
DoCmd.SetWarnings False
DoCmd.RunSQL "SELECT DBA.* INTO BKPRMSTR FROM DBA;"
DoCmd.SetWarnings True
End Function

3.- Run the function.

If it is successful check for a record with an error value as data. Open DBA/Maintain Database and check/fix the record in question.
If the function is not successful. Narrow your query with the "WHERE" statement.

:)

Kelloggs